Attempt to fetch oauth token from git credential #267
Closed
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
sj26
force-pushed
the
auth-token-from-git-credential-helper
branch
from
fc98513 to
eb0272c
Compare
sj26
force-pushed
the
auth-token-from-git-credential-helper
branch
from
eb0272c to
e621d54
Compare
|
No interest? I'll close. |
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.
If we use a git credential helper like osxkeychain with a personal access token for cloning our repositories via HTTPS then we already have a token for reading and writing gists stored securely using git, so maybe we should try using it. It's nice to avoid putting plaintext secrets on our filesystem and avoid polluting ENV with secrets.