Fix Failing GitHub Actions due to Bad Credentials

[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 dessant/lock-threads@v4 action was failing because it did not have the correct credentials.

The changes made ensure that the GitHub Actions workflow uses the correct GitHub secret for the github-token input of the dessant/lock-threads@v4 action.

Summary of Changes

• Created a new GitHub Actions workflow file at .github/workflows/main.yml if it did not already exist.
• Defined a new workflow in this file that is triggered on push and pull_request events.
• Added a job to this workflow that runs the dessant/lock-threads@v4 action.
• Set the github-token input of this action to the value of the GitHub secret that contains the necessary token (github-token: ${{ secrets.GITHUB_TOKEN }}).
• Ensured that the rest of the workflow file is set up correctly, including any other actions that need to be run.

Please review the changes and let me know if any further modifications are required.

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