All of lore.kernel.org
 help / color / mirror / Atom feed
From: "M Hickford via GitGitGadget" <gitgitgadget@gmail.com>
To: git@vger.kernel.org
Cc: peff@peff.net, msuchanek@suse.de, sandals@crustytoothpaste.net,
	lessleydennington@gmail.com, me@ttaylorr.com,
	mjcheetham@github.com, M Hickford <mirth.hickford@gmail.com>,
	M Hickford <mirth.hickford@gmail.com>
Subject: [PATCH v2] doc: gitcredentials: link to helper list
Date: Wed, 21 Jun 2023 07:30:24 +0000	[thread overview]
Message-ID: <pull.1538.v2.git.1687332624780.gitgitgadget@gmail.com> (raw)
In-Reply-To: <pull.1538.git.1685303127237.gitgitgadget@gmail.com>

From: M Hickford <mirth.hickford@gmail.com>

Link to community list of credential helpers. This is useful information
for users.

Describe how OAuth credential helpers work. OAuth is a user-friendly
alternative to personal access tokens and SSH keys. Reduced setup cost
makes it easier for users to contribute to projects across multiple
forges.

Signed-off-by: M Hickford <mirth.hickford@gmail.com>
---
    gitcredentials: link to list of helpers
    
    Add link to list of helpers

Published-As: https://github.com/gitgitgadget/git/releases/tag/pr-1538%2Fhickford%2Fhelpers-v2
Fetch-It-Via: git fetch https://github.com/gitgitgadget/git pr-1538/hickford/helpers-v2
Pull-Request: https://github.com/gitgitgadget/git/pull/1538

Range-diff vs v1:

 1:  49e2a6fc9f2 ! 1:  26818290468 doc: gitcredentials: introduce OAuth helpers
     @@ Metadata
      Author: M Hickford <mirth.hickford@gmail.com>
      
       ## Commit message ##
     -    doc: gitcredentials: introduce OAuth helpers
     +    doc: gitcredentials: link to helper list
      
     -    OAuth credential helpers are widely useful but work differently to other
     -    credential helpers, so worth introducing in the docs.
     +    Link to community list of credential helpers. This is useful information
     +    for users.
      
     -    Link to relevant projects.
     +    Describe how OAuth credential helpers work. OAuth is a user-friendly
     +    alternative to personal access tokens and SSH keys. Reduced setup cost
     +    makes it easier for users to contribute to projects across multiple
     +    forges.
      
          Signed-off-by: M Hickford <mirth.hickford@gmail.com>
      
       ## Documentation/gitcredentials.txt ##
     -@@ Documentation/gitcredentials.txt: $ git config --global credential.helper foo
     +@@ Documentation/gitcredentials.txt: $ git help credential-foo
     + $ git config --global credential.helper foo
       -------------------------------------------
       
     - 
     -+=== OAuth credential helpers
     -+
     -+An alternative to entering passwords or personal access tokens is to use an
     -+OAuth credential helper. Many popular Git hosts support OAuth. The first time
     -+you authenticate, the helper opens a browser window to the host.
     -+Subsequent authentication is non interactive.
     -+
     -+Two cross-platform open-source OAuth credential helpers are:
     ++=== Available helpers
      +
     -+* https://github.com/git-ecosystem/git-credential-manager[Git Credential Manager]
     -+* https://github.com/hickford/git-credential-oauth[git-credential-oauth]
     ++The community maintains a comprehensive
     ++https://git-scm.com/doc/credential-helpers[list of Git credential helpers]
     ++available.
      +
     ++=== OAuth
      +
     ++An alternative to inputting passwords or personal access tokens is to use an
     ++OAuth credential helper. Initial authentication opens a browser window to the
     ++host. Subsequent authentication happens in the background. Many popular Git
     ++hosts support OAuth.
     + 
       CREDENTIAL CONTEXTS
       -------------------
     - 


 Documentation/gitcredentials.txt | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/Documentation/gitcredentials.txt b/Documentation/gitcredentials.txt
index 100f045bb1a..a266870a042 100644
--- a/Documentation/gitcredentials.txt
+++ b/Documentation/gitcredentials.txt
@@ -104,6 +104,18 @@ $ git help credential-foo
 $ git config --global credential.helper foo
 -------------------------------------------
 
+=== Available helpers
+
+The community maintains a comprehensive
+https://git-scm.com/doc/credential-helpers[list of Git credential helpers]
+available.
+
+=== OAuth
+
+An alternative to inputting passwords or personal access tokens is to use an
+OAuth credential helper. Initial authentication opens a browser window to the
+host. Subsequent authentication happens in the background. Many popular Git
+hosts support OAuth.
 
 CREDENTIAL CONTEXTS
 -------------------

base-commit: 79bdd48716a4c455bdc8ffd91d57a18d5cd55baa
-- 
gitgitgadget

  parent reply	other threads:[~2023-06-21  7:30 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
2023-06-21  7:30 ` M Hickford via GitGitGadget [this message]
2023-06-27  8:21   ` [PATCH v2] doc: gitcredentials: link to helper list 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=pull.1538.v2.git.1687332624780.gitgitgadget@gmail.com \
    --to=gitgitgadget@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=lessleydennington@gmail.com \
    --cc=me@ttaylorr.com \
    --cc=mirth.hickford@gmail.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 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.