Fix GitHub Actions Authentication Issue

[sweep-ai]

PR Feedback (click)

• 👍 Sweep Did Well
• 👎 Sweep Needs Improvement
  I created this PR to fix the failing GitHub Actions.## Description
  This PR fixes the GitHub Actions workflow failure due to bad credentials when running the 'dessant/lock-threads@v4' action. The issue was caused by the action not being able to authenticate with GitHub due to missing GitHub token.

The solution involved modifying the GitHub Actions workflow file (.github/workflows/lock-issue.yml) to include the GitHub token in the 'with' section of the 'dessant/lock-threads@v4' action. This allows the action to authenticate with GitHub and perform its operations without any issues.

Summary of Changes

• Modified .github/workflows/lock-issue.yml to include the GitHub token in the 'with' section of the 'dessant/lock-threads@v4' action.

[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 72c5e6d626eb618cbafa47a5ec89a3d92dcb7deb:

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