Article version: Enterprise Server 2.16

This version of GitHub Enterprise will be discontinued on This version of GitHub Enterprise was discontinued on 2020-01-22. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

Git automation with OAuth tokens

You can use OAuth tokens to interact with GitHub Enterprise via automated scripts.

Step 1: Get an OAuth token

Create a personal access token on your application settings page.

Tip: We recommend that you regularly review your authorized integrations. Remove any applications and tokens that haven't been used in a while.

Step 2: Clone a repository

Once you have a token, you can enter it instead of your password when performing Git operations over HTTPS.

For example, on the command line you would enter the following:

$ git clone https://hostname/username/repo.git
Username: your_username
Password: your_token

To avoid these prompts, you can use Git password caching.

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.

Ask a human

Can't find what you're looking for?

Contact us