Fix Authentication Issue in Lock Threads GitHub 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 issue of the failing GitHub Action due to bad credentials. The problem was identified in the GitHub Action workflow responsible for locking threads.

The changes made involve updating the authentication method used in the 'dessant/lock-threads@v4' action within the '.github/workflows/lock-issue.yml' file.

Summary of Changes

• Identified the step in the workflow where 'dessant/lock-threads@v4' is being used.
• Checked the method of authentication being used in this step.
• Ensured that the secret used for authentication is correctly set in the repository settings.
• Checked the documentation for 'dessant/lock-threads@v4' for any known issues or updates related to authentication.
• Modified the workflow to use a different method of authentication, as necessary.

These changes should resolve the issue of the failing GitHub Action and ensure that the lock threads workflow runs successfully.

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

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