Message ID | pull.1396.v3.git.1667912487608.gitgitgadget@gmail.com (mailing list archive) |
---|---|
State | Accepted |
Commit | 54e95b466334e8f6ba4421991cfc189e1291ea87 |
Headers | show |
Series | [v3] Mention that password could be a personal access token. | expand |
On Tue, Nov 08, 2022 at 01:01:27PM +0000, M Hickford via GitGitGadget wrote: > From: M Hickford <mirth.hickford@gmail.com> > > Git asks for a "password", but the user might use a > personal access token or OAuth access token instead. Looks good to me. The only minor issue I noticed was that the commit message should have been prefixed with an area but wasn't. I changed it to the following when queueing: Documentation/gitcredentials.txt: mention password alternatives Thank you for your work. Let's start merging this one down. Thanks, Taylor
diff --git a/Documentation/gitcredentials.txt b/Documentation/gitcredentials.txt index 80517b4eb2c..6df50e8a144 100644 --- a/Documentation/gitcredentials.txt +++ b/Documentation/gitcredentials.txt @@ -17,9 +17,10 @@ DESCRIPTION Git will sometimes need credentials from the user in order to perform operations; for example, it may need to ask for a username and password -in order to access a remote repository over HTTP. This manual describes -the mechanisms Git uses to request these credentials, as well as some -features to avoid inputting these credentials repeatedly. +in order to access a remote repository over HTTP. Some remotes accept +a personal access token or OAuth access token as a password. This +manual describes the mechanisms Git uses to request these credentials, +as well as some features to avoid inputting these credentials repeatedly. REQUESTING CREDENTIALS ----------------------