Add reminder to set BOT_GITHUB_TOKEN secret correctly

[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 remind users to set the BOT_GITHUB_TOKEN secret correctly. This secret should contain a valid GitHub token. If the token is invalid, the 'Lock Threads' workflow will fail with a 'Bad credentials' error.

Summary of Changes

• Added a comment above the 'github-token' input parameter in the .github/workflows/lock-issue.yml file. The comment explains that the BOT_GITHUB_TOKEN secret should contain a valid GitHub token, and that the workflow will fail with a 'Bad credentials' error if the token is invalid.

[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 0b26e708d23b99fcb7dd61d7480851673c283c7c:

[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 alex-page/github-project-automation-plus@v0.8.3
yielded the following error:
##[error]Bad credentials

Here are the logs:

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

[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.1
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)

[kubbot]

This issue is stale because it has been open 60 days with no activity.