Improve error handling for BOT_GITHUB_TOKEN secret

[sweep-ai[bot]]

PR Feedback (click)

• [ ] 👍 Sweep Did Well
• [ ] 👎 Sweep Needs Improvement I created this PR to fix the failing GitHub Actions.## Description This PR improves the error handling in the lock-issue GitHub Actions workflow. Previously, if the BOT_GITHUB_TOKEN secret was not set or invalid, the workflow would fail with a "Bad credentials" error. This error message was not very helpful in diagnosing the problem.

With the changes in this PR, the workflow now checks if the BOT_GITHUB_TOKEN secret is set before the dessant/lock-threads@v4 action is run. If the secret is not set, the workflow fails with a helpful error message.

Summary of Changes

• Added a new step to the .github/workflows/lock-issue.yml workflow that checks if the BOT_GITHUB_TOKEN secret is set.
• If the BOT_GITHUB_TOKEN secret is not set, the new step fails with a helpful error message.

[sweep-ai[bot]]

Rollback Files For Sweep

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

[sweep-ai[bot]]

Sandbox Executions

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

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

Ran GitHub Actions for b9e0c989e6e2c69135d7f621e5f5af28f6f6f8eb:

[sweep-ai[bot]]

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)