From: Eric Sunshine <sunshine@sunshineco.com>
To: M Hickford via GitGitGadget <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, "Jeff King" <peff@peff.net>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"M Hickford" <mirth.hickford@gmail.com>
Subject: Re: [PATCH v2] Mention that password could be a personal access token.
Date: Wed, 2 Nov 2022 06:54:53 -0400 [thread overview]
Message-ID: <CAPig+cQ2Tqt8rzvXsRjCsPFTkbq7B06gq2pourKXi5dKNx8oAA@mail.gmail.com> (raw)
In-Reply-To: <pull.1396.v2.git.1667385022103.gitgitgadget@gmail.com>
On Wed, Nov 2, 2022 at 6:36 AM M Hickford via GitGitGadget
<gitgitgadget@gmail.com> wrote:
> 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>
> ---
> diff --git 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.
I easily understood Ævar's point about these types of secrets all
being different names for a password, but I find the above change
rather confusing when it mentions "multiple passwords". That makes me
think I may need to somehow configure multiple passwords for a site
(even though I know that's not what you meant).
How about a different approach, calling it a "secret" first, and then
defining "secret" as different names for "password". Perhaps something
like this:
Git will sometimes need credentials from the user in order to
perform operations; for example, it may need to ask for a username
and secret in order to access a remote repository over HTTP. The
secret may be a password, passcode, personal access token, OAuth
access token, etc. This manual describes the mechanisms Git uses
to request these credentials, as well as some features to avoid
inputting these credentials repeatedly.
next prev parent reply other threads:[~2022-11-02 10:55 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 ` [PATCH v2] " M Hickford via GitGitGadget
2022-11-02 10:54 ` Eric Sunshine [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAPig+cQ2Tqt8rzvXsRjCsPFTkbq7B06gq2pourKXi5dKNx8oAA@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).