8f964ea2cb
Co-authored-by: Matt Pollard <mattpollard@users.noreply.github.com> Co-authored-by: Grace Park <gracepark@github.com> Co-authored-by: Steve Guntrip <12534592+stevecat@users.noreply.github.com> Co-authored-by: Robert Sese <sese@github.com> Co-authored-by: Peter Bengtsson <peterbe@github.com> Co-authored-by: Rachael Sewell <rachmari@github.com>
49 lines
1.8 KiB
Markdown
49 lines
1.8 KiB
Markdown
---
|
|
title: Git automation with OAuth tokens
|
|
redirect_from:
|
|
- /articles/git-over-https-using-oauth-token/
|
|
- /articles/git-over-http-using-oauth-token/
|
|
- /articles/git-automation-with-oauth-tokens
|
|
intro: 'You can use OAuth tokens to interact with {% data variables.product.product_name %} via automated scripts.'
|
|
versions:
|
|
fpt: '*'
|
|
ghes: '*'
|
|
ghae: '*'
|
|
ghec: '*'
|
|
shortTitle: Automate with OAuth tokens
|
|
---
|
|
|
|
## Step 1: Get an OAuth token
|
|
|
|
Create a personal access token on your application settings page. For more information, see "[Creating a personal access token](/github/authenticating-to-github/creating-a-personal-access-token)."
|
|
|
|
{% tip %}
|
|
|
|
{% ifversion fpt or ghec %}
|
|
**Tips:**
|
|
- You must verify your email address before you can create a personal access token. For more information, see "[Verifying your email address](/articles/verifying-your-email-address)."
|
|
- {% data reusables.user_settings.review_oauth_tokens_tip %}
|
|
{% else %}
|
|
**Tip:** {% data reusables.user_settings.review_oauth_tokens_tip %}
|
|
{% endif %}
|
|
|
|
{% endtip %}
|
|
|
|
{% ifversion fpt or ghec %}{% data reusables.user_settings.removes-personal-access-tokens %}{% endif %}
|
|
|
|
## Step 2: Clone a repository
|
|
|
|
{% data reusables.command_line.providing-token-as-password %}
|
|
|
|
To avoid these prompts, you can use Git password caching. For information, see "[Caching your GitHub credentials in Git](/github/getting-started-with-github/caching-your-github-credentials-in-git)."
|
|
|
|
{% warning %}
|
|
|
|
**Warning**: Tokens have read/write access and should be treated like passwords. If you enter your token into the clone URL when cloning or adding a remote, Git writes it to your _.git/config_ file in plain text, which is a security risk.
|
|
|
|
{% endwarning %}
|
|
|
|
## Further reading
|
|
|
|
- "[Authorizing OAuth Apps](/developers/apps/authorizing-oauth-apps)"
|