Fix GitHub Actions Failure Due to Bad Credentials

[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 issue of the GitHub Actions workflow failing due to bad credentials. The 'Lock Threads' workflow was failing because it was trying to use the BOT_GITHUB_TOKEN secret, which was either missing or invalid.

The solution implemented in this PR is to add a conditional check in the workflow file to ensure that the BOT_GITHUB_TOKEN secret is not empty before the workflow runs. If the secret is empty, the step that uses the dessant/lock-threads@v4 action is skipped, preventing the workflow from failing.

Summary of Changes

• Modified the .github/workflows/lock-issue.yml file to add a conditional check for the BOT_GITHUB_TOKEN secret. The check is added to the step that uses the dessant/lock-threads@v4 action.

Please review the changes and let me know if any further modifications are required.

[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 d2187a490fba9b70edea6d8c35956a872c7a868f:

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