Add comment about BOT_GITHUB_TOKEN in lock-issue workflow #97
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 'Lock Threads' GitHub Actions workflow failing due to bad credentials. The issue was traced back to the BOT_GITHUB_TOKEN secret, which is used in the .github/workflows/lock-issue.yml file.
The 'Bad credentials' error suggests that the BOT_GITHUB_TOKEN secret is either missing or invalid. Therefore, a comment has been added in the .github/workflows/lock-issue.yml file to remind future maintainers about the importance of this secret and to ensure that it is set to a valid GitHub token.
Summary of Changes