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 of failing GitHub Actions due to bad credentials. The problem was identified to be with the 'dessant/lock-threads@v4' command in the GitHub Actions workflow file. The command was not properly authenticated, causing the workflow to fail.

The solution involved modifying the workflow file to include the correct token for authentication. The GitHub token that is automatically created for GitHub Actions was used.

Summary of Changes

• Modified the '.github/workflows/main.yml' file to include the correct token for the 'dessant/lock-threads@v4' command.
• Added a 'with' directive for the command, if it did not already exist.
• Within the 'with' directive, added a line for the token: 'token: ${{ secrets.GITHUB_TOKEN }}'.

These changes should resolve the issue and allow the GitHub Actions workflow to run successfully.

[sweep-ai]

Rollback Files For Sweep

• Rollback changes to .github/workflows/main.yml

[sweep-ai]

Sandbox Executions

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