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 was not provided with the correct credentials.

The changes made involve modifying the GitHub Actions workflow file to ensure the correct credentials are being used. If the action was being run with hard-coded credentials, these were replaced with a reference to a GitHub secret. If the action was already being run with a GitHub secret, the secret was checked to ensure it was correctly set up in the repository settings. If the action was being run without any credentials, a 'with' section was added to provide the necessary credentials.

Summary of Changes

• Modified .github/workflows/main.yml to ensure the correct credentials are being used for the dessant/lock-threads@v4 action.
• Replaced hard-coded credentials with a reference to a GitHub secret, if applicable.
• Checked the 'GITHUB_TOKEN' secret in the repository settings, if applicable.
• Added a 'with' section to provide necessary credentials, if applicable.

[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

Making changes according to plan... (step 3/3)