Add comment about BOT_GITHUB_TOKEN secret in lock-issue workflow

[sweep-ai-deprecated]

PR Feedback (click)

• 👍 Sweep Did Well
• 👎 Sweep Needs Improvement
  I created this PR to fix the failing GitHub Actions.## Description
  This PR adds a comment in the .github/workflows/lock-issue.yml file to provide clarity about the BOT_GITHUB_TOKEN secret. The comment explains that the secret needs to be set in the repository settings and must contain a valid GitHub token. It also mentions that if the secret is not set or contains an invalid token, the workflow will fail with a "Bad credentials" error.

Summary of Changes

• Added a comment in the .github/workflows/lock-issue.yml file about the BOT_GITHUB_TOKEN secret.

[sweep-ai-deprecated]

Rollback Files For Sweep

• Rollback changes to .github/workflows/lock-issue.yml
• Rollback changes to .github/workflows/lock-issue.yml

[sweep-ai-deprecated]

Sandbox Executions

• Running GitHub Actions for .github/workflows/lock-issue.yml ✓

Check .github/workflows/lock-issue.yml with contents:

Ran GitHub Actions for d2917fd7706ae5079e0f1011414b6ba2ead96f3e:

[sweep-ai-deprecated]

Fixing PR: track the progress here.

I'm currently fixing this PR to address the following:

[Sweep GHA Fix] The GitHub Actions run failed with the following error logs:

The command:
Run contributor-assistant/github-action@v2.3.0
yielded the following error:
##[error]graphql call to get the committers details failed: HttpError: Bad credentials

Here are the logs:
CLA Assistant GitHub Action bot has started the process

Making changes according to plan... (step 3/3)