From: "M Hickford via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: M Hickford <mirth.hickford@gmail.com>,
M Hickford <mirth.hickford@gmail.com>
Subject: [PATCH] Mention that password could be a personal access token.
Date: Thu, 27 Oct 2022 04:45:47 +0000 [thread overview]
Message-ID: <pull.1396.git.1666845947898.gitgitgadget@gmail.com> (raw)
From: M Hickford <mirth.hickford@gmail.com>
These days, the 'password' for a software forge might be personal access
token or OAuth access token.
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-v1
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1396/hickford/more-about-credentials-v1
Pull-Request: https://github.com/gitgitgadget/git/pull/1396
Documentation/git-credential.txt | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Documentation/git-credential.txt b/Documentation/git-credential.txt
index f18673017f5..f3bf0bef54b 100644
--- a/Documentation/git-credential.txt
+++ b/Documentation/git-credential.txt
@@ -142,7 +142,9 @@ Git understands the following attributes:
`password`::
- The credential's password, if we are asking it to be stored.
+ The credential's password, if we are asking it to be stored. If the
+ host is a software forge, this could also be a personal access
+ token or OAuth access token.
`url`::
base-commit: 1fc3c0ad407008c2f71dd9ae1241d8b75f8ef886
--
gitgitgadget
next reply other threads:[~2022-10-27 4:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 4:45 M Hickford via GitGitGadget [this message]
2022-10-27 17:40 ` [PATCH] Mention that password could be a personal access token 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 ` [PATCH v2] " M Hickford via GitGitGadget
2022-11-02 10:54 ` 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.git.1666845947898.gitgitgadget@gmail.com \
--to=gitgitgadget@gmail.com \
--cc=git@vger.kernel.org \
--cc=mirth.hickford@gmail.com \
/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.