Fix GitHub Actions Credentials Issue #15
Open
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 |
|
The command: |
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 address this rule:
"None"
Description
This PR fixes the "Bad credentials" error that was occurring during the GitHub Actions run. The error was due to the incorrect or missing GitHub token in the
dessant/lock-threads@v4action.The changes in this PR ensure that the correct GitHub token (
BOT_GITHUB_TOKEN) is used in thedessant/lock-threads@v4action.Summary of Changes
dessant/lock-threads@v4action to use theBOT_GITHUB_TOKEN.BOT_GITHUB_TOKENsecret is set in the repository settings and has the necessary permissions.Please review and merge the changes.