Add check for BOT_GITHUB_TOKEN secret in Lock Threads 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 adds a check at the beginning of the Lock Threads workflow that verifies if the BOT_GITHUB_TOKEN secret is set. If it is not set, the workflow fails with a clear error message. This makes it easier to diagnose and fix the issue if the workflow fails due to the BOT_GITHUB_TOKEN secret not being set.

Summary of Changes

• Modified .github/workflows/lock-issue.yml to add a step that checks if the BOT_GITHUB_TOKEN secret is set.

This change should help prevent the workflow from failing due to bad credentials in the future.

[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 8132312a41742616b2b77634310c43aa332783e5:

[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

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