Fix GitHub Actions Authentication 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 when running the dessant/lock-threads@v4 action. The error was caused by the action not being correctly authenticated with a GitHub token.

The solution involved modifying the .github/workflows/lock-issue.yml file to correctly set the github-token input parameter for the dessant/lock-threads@v4 action. This ensures that the action is correctly authenticated, preventing the "Bad credentials" error.

Summary of Changes

• Modified .github/workflows/lock-issue.yml to add the github-token input parameter to the dessant/lock-threads@v4 action and set it to the 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 4423963b5d30162f7dc17b41234e01754ccc23f1:

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