From: M Hickford <mirth.hickford@gmail.com>
Date: Tue, 01 Nov 2022 03:54:46 GMT
Subject: Re: [PATCH] Mention that password could be a personal access token.
Message-ID: <CAGJzqs=PovTFeVFJAT1HLcKQxHdRjozUACh3Z-x8ih6yuYSb7w@mail.gmail.com>
In-Reply-To: <xmqqk04lmagy.fsf@gitster.g>

On Thu, 27 Oct 2022 at 18:40, Junio C Hamano <gitster@pobox.com> wrote:

> Also, I wonder if the specific "it can be access token and not
> password" is something worth adding.

Personal access tokens are ubiquitous nowadays, maybe even more common
than passwords since GitHub disabled passwords last year. I wanted
to acknowledge this in the docs, even if Git's own behaviour hasn't
changed. Maybe the introduction to
https://git-scm.com/docs/gitcredentials would be a better place to do
that?

     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. **The
server may accept or expect a personal access token instead of a
password.**

[1] https://github.blog/changelog/2021-08-12-git-password-authentication-is-shutting-down/