Fix GitHub Actions Authentication Error

[sweep-ai]

PR Feedback (click)

• 👍 Sweep Did Well
• 👎 Sweep Needs Improvement
  I created this PR to fix the failing GitHub Actions.## Description
  This PR fixes the "Bad credentials" error that was occurring in the GitHub Actions workflow. The error was due to the dessant/lock-threads@v4 action not being able to authenticate with GitHub.

The issue was resolved by ensuring that the action has the correct GitHub token to authenticate with. This was done by modifying the workflow file to pass the GitHub token from the repository's secrets to the action.

Summary of Changes

• Modified the workflow file that contains the dessant/lock-threads@v4 action.
• Added a with section under the action if it was not already present.
• Ensured that the with section contains the line github-token: ${{ secrets.GITHUB_TOKEN }}, which passes the GitHub token to the action. If this line was not present, it was added. If a different token was being used, it was changed to use the default GitHub token.

Please review the changes and let me know if there are any issues or further changes needed.

[sweep-ai]

Rollback Files For Sweep

• Rollback changes to path_to_workflow_file

[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 alex-page/[email protected]
yielded the following error:
##[error]Bad credentials

Here are the logs:

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

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

[kubbot]

This issue is stale because it has been open 60 days with no activity.