Fix 'Bad credentials' error 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 addresses the 'Bad credentials' error that was occurring in the Lock Threads workflow. The error was due to the BOT_GITHUB_TOKEN secret being either missing or invalid.

The changes in this PR add a condition to the workflow to check if the BOT_GITHUB_TOKEN secret is not empty before running the dessant/lock-threads@v4 action. This prevents the workflow from running if the secret is not set, thereby avoiding the 'Bad credentials' error.

Summary of Changes

• Modified the .github/workflows/lock-issue.yml file to add a condition to check if the BOT_GITHUB_TOKEN secret is not empty before running the dessant/lock-threads@v4 action.

Please review and merge the changes.

[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 049a2502aa76e804eb7d27d4ea3c710d9a0e324d:

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