Fix GitHub Actions Authentication Issue #72
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-threads.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) |
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 with the failing GitHub Actions due to bad credentials. The problem was identified to be with the
dessant/lock-threads@v4action in the.github/workflows/lock-threads.ymlworkflow file.The issue was resolved by ensuring that the correct secrets are being used for authentication. The secrets used by the
cla.ymlandrelease.ymlworkflows, which aresecrets.BOT_GITHUB_TOKENandsecrets.REDBOT_GITHUB_TOKENrespectively, were used to authenticate thedessant/lock-threads@v4action.Summary of Changes
.github/workflows/lock-threads.ymlworkflow file to use the correct secrets for authentication.envsubsection in the section that uses thedessant/lock-threads@v4action to use thesecrets.BOT_GITHUB_TOKENsecret for authentication.envsubsection was already present, ensured that it uses the correct secret for authentication.