From: M Hickford <mirth.hickford@gmail.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
M Hickford via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org, peff@peff.net, msuchanek@suse.de,
lessleydennington@gmail.com, me@ttaylorr.com,
mjcheetham@github.com, M Hickford <mirth.hickford@gmail.com>
Subject: Re: [PATCH] doc: gitcredentials: introduce OAuth helpers
Date: Wed, 21 Jun 2023 07:28:01 +0100 [thread overview]
Message-ID: <CAGJzqs=NbfCt78NtANCxTNJxWG+Oc4bLCjhSSQhrOgr0YWuucg@mail.gmail.com> (raw)
In-Reply-To: <ZHPa27fbAoKL0uGj@tapette.crustytoothpaste.net>
> I expect, however, that functionally, that will be difficult to do,
> given the fact that OAuth typically requires registration with the
> remote system, and thus we'd intrinsically be prioritizing some
> well-known forges over less-known or personally-hosted forges, which
> we've traditionally tried not to do. For example, your
> git-credential-oauth contains a hard-coded list of 11 forges
Forge diversity is my motivation! Consider the average Git user. They
contribute to several projects on GitHub. They are deterred from
contributing to worthy projects elsewhere by the setup cost of
configuring personal access tokens or SSH keys. To use five forges
from three machines, you have to generate 15 personal access tokens or
upload SSH keys 15 times. Whereas a git-credential-oauth user can
contribute to projects on many popular hosts without any setup. That's
progress surely.
next prev parent reply other threads:[~2023-06-21 6:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-28 19:45 [PATCH] doc: gitcredentials: introduce OAuth helpers M Hickford via GitGitGadget
2023-05-28 22:51 ` brian m. carlson
2023-05-29 9:50 ` M Hickford
2023-06-21 6:28 ` M Hickford [this message]
2023-06-21 7:30 ` [PATCH v2] doc: gitcredentials: link to helper list M Hickford via GitGitGadget
2023-06-27 8:21 ` Jeff King
2023-07-08 20:36 ` [PATCH v3] " M Hickford via GitGitGadget
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='CAGJzqs=NbfCt78NtANCxTNJxWG+Oc4bLCjhSSQhrOgr0YWuucg@mail.gmail.com' \
--to=mirth.hickford@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=lessleydennington@gmail.com \
--cc=me@ttaylorr.com \
--cc=mjcheetham@github.com \
--cc=msuchanek@suse.de \
--cc=peff@peff.net \
--cc=sandals@crustytoothpaste.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 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).