From: "M Hickford via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: "Jeff King" <peff@peff.net>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"M Hickford" <mirth.hickford@gmail.com>,
"M Hickford" <mirth.hickford@gmail.com>
Subject: [PATCH v2] Mention that password could be a personal access token.
Date: Wed, 02 Nov 2022 10:30:21 +0000 [thread overview]
Message-ID: <pull.1396.v2.git.1667385022103.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.1396.git.1666845947898.gitgitgadget@gmail.com>
From: M Hickford <mirth.hickford@gmail.com>
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@gmail.com>
---
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
next prev parent reply other threads:[~2022-11-02 10:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 4:45 [PATCH] Mention that password could be a personal access token M Hickford via GitGitGadget
2022-10-27 17:40 ` Junio C Hamano
2022-10-27 20:21 ` Jeff King
2022-10-27 21:48 ` Junio C Hamano
2022-11-01 3:54 ` M Hickford
2022-11-01 7:58 ` Ævar Arnfjörð Bjarmason
2022-11-01 10:27 ` M Hickford
2022-11-02 10:30 ` M Hickford via GitGitGadget [this message]
2022-11-02 10:54 ` [PATCH v2] " Eric Sunshine
2022-11-02 15:44 ` Junio C Hamano
2022-11-02 15:51 ` Eric Sunshine
2022-11-02 17:30 ` Philip Oakley
2022-11-08 12:11 ` M Hickford
2022-11-08 13:01 ` [PATCH v3] " M Hickford via GitGitGadget
2022-11-08 21:48 ` Taylor Blau
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pull.1396.v2.git.1667385022103.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=mirth.hickford@gmail.com \
--cc=peff@peff.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.