From: M Hickford <mirth.hickford@xxxxxxxxx>
These days, the 'password' for a software forge might be personal access
token or OAuth access token. These are popular, so worth clarifying that
Git treats them just the same.
Signed-off-by: M Hickford <mirth.hickford@xxxxxxxxx>
---
Mention that password could be a personal access token.
These days, the 'password' for a software forge might be personal access
token or OAuth access token.
Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1396%2Fhickford%2Fmore-about-credentials-v2
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1396/hickford/more-about-credentials-v2
Pull-Request: https://github.com/gitgitgadget/git/pull/1396
Range-diff vs v1:
1: fef359f533a < -: ----------- Mention that password could be a personal access token.
-: ----------- > 1: 0bb69988ad7 Mention that password could be a personal access token.
Documentation/gitcredentials.txt | 3 +++
1 file changed, 3 insertions(+)
diff --git a/Documentation/gitcredentials.txt b/Documentation/gitcredentials.txt
index 80517b4eb2c..402e067a6ca 100644
--- a/Documentation/gitcredentials.txt
+++ b/Documentation/gitcredentials.txt
@@ -21,6 +21,9 @@ 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.
+Some repositories accept multiple passwords, including personal access
+tokens and OAuth access tokens. Git handles all of these the same.
+
REQUESTING CREDENTIALS
----------------------
base-commit: c03801e19cb8ab36e9c0d17ff3d5e0c3b0f24193
--
gitgitgadget
