Add comment about BOT_GITHUB_TOKEN in lock-issue workflow

[sweep-ai]

PR Feedback (click)

• 👍 Sweep Did Well
• 👎 Sweep Needs Improvement
  I created this PR to fix the failing GitHub Actions.## Description
  This PR addresses the issue of the 'Lock Threads' GitHub Actions workflow failing due to bad credentials. The issue was traced back to the BOT_GITHUB_TOKEN secret, which is used in the .github/workflows/lock-issue.yml file.

The 'Bad credentials' error suggests that the BOT_GITHUB_TOKEN secret is either missing or invalid. Therefore, a comment has been added in the .github/workflows/lock-issue.yml file to remind future maintainers about the importance of this secret and to ensure that it is set to a valid GitHub token.

Summary of Changes

• Added a comment in .github/workflows/lock-issue.yml to explain the importance of the BOT_GITHUB_TOKEN secret.

[sweep-ai]

Rollback Files For Sweep

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

[sweep-ai]

Sandbox Executions

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

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

Ran GitHub Actions for 32421ee8efc1318f687477f01d4b7cd26c72af0f:

[sweep-ai]

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)