caaee7a124
* Add back changes from prior to purge * Manually fix some invalid Liquid * Updoot render-content * Improve test messages to show correct output * Run el scripto * Pass the remaining test
1.7 KiB
title, redirect_from, intro, versions
| title | redirect_from | intro | versions | |||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Git automation with OAuth tokens |
|
You can use OAuth tokens to interact with {% data variables.product.product_name %} via automated scripts. |
|
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."
{% tip %}
{% if currentVersion == "free-pro-team@latest" %} Tips:
- You must verify your email address before you can create a personal access token. For more information, see "Verifying your email address."
- {% data reusables.user_settings.review_oauth_tokens_tip %} {% else %} Tip: {% data reusables.user_settings.review_oauth_tokens_tip %} {% endif %}
{% endtip %}
{% if currentVersion == "free-pro-team@latest" %}{% 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."
{% 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 %}