Update npm-bump-version.yml secret name #15
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
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.
I think we just need to switch out the name of the secret, as described in the 1st section here if I understand correctly?
If this doesn't work we can switch to Apps but wanted to try this first
For Actions, you should almost never have to use an external token. Actions expose a token in the ${{ secrets.GITHUB_TOKEN }} environment variable. This token is automatically generated by GitHub and has permissions for the repository it is running in.Edit: Failed to give context for this one: This is the ticket that reports the problem. npm-bump-version workflow for this package fails with
Error: fatal: could not read Username for 'https://github.com/': terminal prompts disabled, which points to a problem with authorization with tokens.