Fix Failing GitHub Action 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 the failing GitHub Action dessant/lock-threads@v4 due to bad credentials. The problem was identified to be an outdated or incorrect token being used for authentication in the GitHub Action configuration.

The solution implemented in this PR involves updating the token used by the action. The token has been replaced with a new, valid one that is stored as a secret in the repository settings. This ensures the security of the token as it is not exposed in any code or logs.

Summary of Changes

• Located the GitHub Action configuration file using the dessant/lock-threads@v4 action in the .github/workflows directory.
• Identified the section in the configuration file where the token for the action is specified.
• Replaced the outdated token with a reference to the new token stored as a secret in the repository settings.

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/action_file.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 2/3)