Fix GitHub Actions Bad Credentials Error #93
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![sweep-ai[bot]](https://avatars.githubusercontent.com/in/307814?s=60&v=4){kind=small}
Rollback Files For Sweep
|
Sandbox Executions
Check .github/workflows/lock-issue.yml with contents: |
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: Making changes according to plan... (step 3/3) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Feedback (click)
I created this PR to fix the failing GitHub Actions.## Description
This PR addresses the issue of the GitHub Actions workflow failing due to bad credentials. The 'Lock Threads' workflow, defined in the .github/workflows/lock-issue.yml file, uses the dessant/lock-threads@v4 action, which requires a GitHub token to function correctly. The error message "Bad credentials" suggested that the token provided to the action was either incorrect or missing.
The 'github-token' parameter was previously set to use the 'BOT_GITHUB_TOKEN' secret. This secret was either not defined in the repository settings, or it contained an incorrect token, causing the action to fail.
Summary of Changes
The .github/workflows/lock-issue.yml file has been modified to use the 'GITHUB_TOKEN' secret for the 'github-token' parameter, instead of 'BOT_GITHUB_TOKEN'. The 'GITHUB_TOKEN' is a built-in secret that GitHub automatically creates for every repository. This secret contains a token that has the necessary permissions to perform most common tasks, and it should be sufficient for the lock-threads action.
The specific change made is as follows: