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 addresses the issue with the GitHub Actions workflow failing due to bad credentials when running the dessant/lock-threads@v4 action. The issue was that the action was not able to authenticate with GitHub.

Summary of Changes

• Modified the .github/workflows/lock-issue.yml file to pass the GitHub token to the dessant/lock-threads@v4 action. This allows the action to authenticate with GitHub and perform the necessary operations.

with:
  github-token: ${{ secrets.GITHUB_TOKEN }}

The secrets.GITHUB_TOKEN is a built-in secret in GitHub Actions, and it is automatically created by GitHub. It is used to authenticate in order to perform operations on behalf of the GitHub Actions bot.

[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 06b19d24230913ce557bd8bb1239232127b64bc0:

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