Repository navigation
docs: read the packages token from gh in the gradle example, so nobody keeps a pat on disk - #64
Merged
Merged
Conversation
…y keeps a pat on disk
This file contains hidden or 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.
The install guide had a consumer paste a classic PAT into
~/.gradle/gradle.properties: a second copy of a GitHub secret that expires and nothing renews. The Gradle example now falls back togh auth token, read on every build, so setup is onegh auth refresh -s read:packages.gpr.user/gpr.keystill win, for whoever has no gh. Without gh or signed out the helper yields nothing and the build gets GitHub's 401. The user name is a constant because GitHub Packages checks only the token. Maven is unchanged: it has no hook to run a command for a credential.