On Wed, Nov 2, 2022 at 11:45 AM Junio C Hamano <gitster@xxxxxxxxx> wrote:
> On Wed, Nov 2, 2022 at 3:55 AM Eric Sunshine <sunshine@xxxxxxxxxxxxxx> wrote:
> > How about a different approach, calling it a "secret" first, and then
> > defining "secret" as different names for "password".
>
> Or more directly, say "password" and parenthetically add that some hosting
> sites may call it with different names like "personal tokens"?
I tried the parenthetical approach first but the sentence structure
became too complex and more difficult to understand. Having a separate
sentence helped simplify. That said, perhap 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 password in order to access a remote repository over HTTP. In
place of a password, some sites may instead provide a passcode,
personal access token, OAuth access token, etc. This manual...
