From 71f290289184e55fe2f6ecd3a4ce8eaf3ec5ca48 Mon Sep 17 00:00:00 2001 From: Gary Munnelly Date: Thu, 13 May 2021 21:05:53 +0100 Subject: [PATCH 1/3] Added section on caching PAT --- .../creating-a-personal-access-token.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content/github/authenticating-to-github/creating-a-personal-access-token.md b/content/github/authenticating-to-github/creating-a-personal-access-token.md index c94cfbe856..f0b26e214c 100644 --- a/content/github/authenticating-to-github/creating-a-personal-access-token.md +++ b/content/github/authenticating-to-github/creating-a-personal-access-token.md @@ -63,6 +63,10 @@ Personal access tokens can only be used for HTTPS Git operations. If your reposi If you are not prompted for your username and password, your credentials may be cached on your computer. You can [update your credentials in the Keychain](/github/getting-started-with-github/updating-credentials-from-the-macos-keychain) to replace your old password with the token. +### Caching a token with git + +Rather than manually entering your personal access token every time you perform an HTTPS Git operation, you can cache your token with a Git client. Git will temporarily store your credentials in memory until an expiry interval has passed. You can also store the token in a plain text file that Git can read before every request. Information on caching your personal access token can be found in [Caching your GitHub credentials in Git](https://docs.github.com/en/github/getting-started-with-github/caching-your-github-credentials-in-git). + ### Further reading - "[About authentication to GitHub](/github/authenticating-to-github/about-authentication-to-github)" From 69c513bc90dc7258eb5b1a0ac1152b4fb1630a27 Mon Sep 17 00:00:00 2001 From: Laura Coursen Date: Tue, 18 May 2021 15:23:52 -0500 Subject: [PATCH 2/3] Add :nail_care: --- .../creating-a-personal-access-token.md | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/content/github/authenticating-to-github/creating-a-personal-access-token.md b/content/github/authenticating-to-github/creating-a-personal-access-token.md index f0b26e214c..4ffe5a41ae 100644 --- a/content/github/authenticating-to-github/creating-a-personal-access-token.md +++ b/content/github/authenticating-to-github/creating-a-personal-access-token.md @@ -63,9 +63,7 @@ Personal access tokens can only be used for HTTPS Git operations. If your reposi If you are not prompted for your username and password, your credentials may be cached on your computer. You can [update your credentials in the Keychain](/github/getting-started-with-github/updating-credentials-from-the-macos-keychain) to replace your old password with the token. -### Caching a token with git - -Rather than manually entering your personal access token every time you perform an HTTPS Git operation, you can cache your token with a Git client. Git will temporarily store your credentials in memory until an expiry interval has passed. You can also store the token in a plain text file that Git can read before every request. Information on caching your personal access token can be found in [Caching your GitHub credentials in Git](https://docs.github.com/en/github/getting-started-with-github/caching-your-github-credentials-in-git). +Instead of manually entering your PAT for every HTTPS Git operation, you can cache your token with a Git client. Git will temporarily store your credentials in memory until an expiry interval has passed. You can also store the token in a plain text file that Git can read before every request. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)." ### Further reading From 05d341b126c9bf40c8c595842c5134685c6dafce Mon Sep 17 00:00:00 2001 From: Laura Coursen Date: Tue, 18 May 2021 15:29:19 -0500 Subject: [PATCH 3/3] Add :nail_care: --- .../creating-a-personal-access-token.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/github/authenticating-to-github/creating-a-personal-access-token.md b/content/github/authenticating-to-github/creating-a-personal-access-token.md index 4ffe5a41ae..61a8e5775c 100644 --- a/content/github/authenticating-to-github/creating-a-personal-access-token.md +++ b/content/github/authenticating-to-github/creating-a-personal-access-token.md @@ -63,7 +63,7 @@ Personal access tokens can only be used for HTTPS Git operations. If your reposi If you are not prompted for your username and password, your credentials may be cached on your computer. You can [update your credentials in the Keychain](/github/getting-started-with-github/updating-credentials-from-the-macos-keychain) to replace your old password with the token. -Instead of manually entering your PAT for every HTTPS Git operation, you can cache your token with a Git client. Git will temporarily store your credentials in memory until an expiry interval has passed. You can also store the token in a plain text file that Git can read before every request. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)." +Instead of manually entering your PAT for every HTTPS Git operation, you can cache your PAT with a Git client. Git will temporarily store your credentials in memory until an expiry interval has passed. You can also store the token in a plain text file that Git can read before every request. For more information, see "[Caching your {% data variables.product.prodname_dotcom %} credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)." ### Further reading