Fix GitHub Actions Bad Credentials Error

[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 using an invalid or missing GitHub token.

The changes in this PR ensure that a valid GitHub token is provided to the dessant/lock-threads@v4 action in the .github/workflows/lock-issue.yml file.

Summary of Changes

• Modified the .github/workflows/lock-issue.yml file to replace the BOT_GITHUB_TOKEN secret with a valid GitHub token.

Please note that you will need to replace YOUR_VALID_GITHUB_TOKEN with your actual valid GitHub token in the repository's secrets for the changes to take effect.

[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 17e0ef96147fcfe45d7fed35b4e52f61330d6163:

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