Improve error handling for missing BOT_GITHUB_TOKEN secret

[sweep-ai]

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.yml GitHub Actions workflow. Previously, if the BOT_GITHUB_TOKEN secret was missing or incorrect, the workflow would fail with a "Bad credentials" error. This error message was not very descriptive and made it difficult to diagnose the issue.

With this change, if the BOT_GITHUB_TOKEN secret is missing, the workflow will fail with the error message "Error: BOT_GITHUB_TOKEN secret is not set." This makes it easier to diagnose and fix the issue.

Summary of Changes

• Modified the github-token parameter of the lock-threads action in the lock-issue.yml workflow to include a check that the BOT_GITHUB_TOKEN secret is set. If the secret is not set, the workflow will fail with a descriptive error message.

[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 79e79618594bf3b707a7abfc344f106624ba4453:

[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/[email protected]
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

Generating plan by analyzing files... (step 2/3)