Fix GitHub Actions Run by Correcting Environment Variables #16
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 addresses the issue of the GitHub Actions run failing due to bad credentials. The problem was traced back to the environment variables used in the
.github/workflows/release.yml
file.The
goreleaser/goreleaser-action@v4
action was configured to use certain environment variables such asUSERNAME
,GITHUB_TOKEN
, andFURY_TOKEN
. These environment variables were not set correctly, causing theusthe/[email protected]
action to fail.Summary of Changes
USERNAME
,GITHUB_TOKEN
, andFURY_TOKEN
in thegoreleaser/goreleaser-action@v4
action configuration.usthe/[email protected]
action.These changes should fix the GitHub Actions run and prevent the
Bad credentials
error from occurring in the future.