Update GitHub Token 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 updates the GitHub token used in the Lock Threads workflow. The previous token was causing the workflow to fail due to bad credentials.

The changes involve updating the secret used in the .github/workflows/lock-issue.yml file from 'BOT_GITHUB_TOKEN' to 'NEW_GITHUB_TOKEN'.

Summary of Changes

• Updated the secret used for the GitHub token in the Lock Threads workflow (.github/workflows/lock-issue.yml)

Please ensure that the 'NEW_GITHUB_TOKEN' secret is set in the repository settings and contains a valid GitHub token.

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

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