fix: GitHub token for Homebrew tap #50
Merged
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
The token needs to be one that has access to write to the norwoodj/homebrew-tap repository. The 'secrets.GITHUB_TOKEN' token only has access to write to the current repository.
norwoodj
approved these changes
Aug 7, 2020
|
Thanks a ton @sc250024! |
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.
Description
This release action (https://github.com/norwoodj/helm-docs/runs/955815074) failed because the token is wrong.
The token needs to be one that has access to write to the https://github.com/norwoodj/homebrew-tap repository. Using the default
secrets.GITHUB_TOKENtoken is wrong because it only has access to write to the current repository, and nothing else.@norwoodj Can you create a personal access token with the
reposcope enabled as it says in the instructions here please (https://goreleaser.com/environment/#api-tokens) ? It should go in a secret namedNORWOODJ_ORG_TOKEN.