-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix GitHub Actions Failing Due to Bad Credentials #52
Open
sweep-ai
wants to merge
3
commits into
main
Choose a base branch
from
sweep/github-actions-credentials_5
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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
Rollback Files For Sweep
|
Sandbox Executions
Check .github/workflows/stale.yml with contents:
Check .github/workflows/release.yml with contents:
Check .github/workflows/gosec.yml with contents:
Check .github/workflows/cla.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: |
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: |
This issue is stale because it has been open 60 days with no activity. |
kubbot
added
the
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
label
May 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
lifecycle/stale
Denotes an issue or PR has remained open with no activity and has become stale.
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 GitHub Actions failing due to bad credentials. The error was specifically coming from the
dessant/lock-threads@v4
action. TheBOT_GITHUB_TOKEN
was replaced with the defaultGITHUB_TOKEN
provided by GitHub Actions in the workflow files where it was used.Summary of Changes
.github/workflows/stale.yml
to useGITHUB_TOKEN
instead ofBOT_GITHUB_TOKEN
..github/workflows/release.yml
to useGITHUB_TOKEN
instead ofBOT_GITHUB_TOKEN
.BOT_GITHUB_TOKEN
was used in.github/workflows/gosec.yml
, it was replaced withGITHUB_TOKEN
..github/workflows/cla.yml
to useGITHUB_TOKEN
instead ofBOT_GITHUB_TOKEN
. IfREDBOT_GITHUB_TOKEN
was also a GitHub token and it was causing issues, it was replaced as well.These changes should resolve the issue of GitHub Actions failing due to bad credentials.