Fix 'Bad credentials' error in lock-threads action

[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 dessant/lock-threads@v4 GitHub Action. The issue was due to the use of an incorrect or expired GitHub token.

The changes in this PR include:

• Updated the GITHUB_TOKEN used in the dessant/lock-threads@v4 action to use the correct token. This was done in the .github/workflows/lock-issue.yml file.

Summary of Changes

• Modified .github/workflows/lock-issue.yml to use the correct GitHub token for 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 d036dd89f7ad60555d7ac80dbe7c05feb7ed5448:

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