Warning: Treat your access tokens like passwords.
To access GitHub from the command line, consider using GitHub CLI or Git Credential Manager instead of creating a personal access token.
When using a personal access token in a script, consider storing your token as a secret and running your script through GitHub Actions. For more information, see "Encrypted secrets."
If these options are not possible, consider using another service such as the 1Password CLI to store your token securely.
Personal access token are an alternative to using passwords for authentication to GitHub Enterprise Server when using the GitHub API or the command line. Personal access tokens are intended to access GitHub resources on behalf of yourself. To access resources on behalf of an organization, or for long-lived integrations, you should use a GitHub App. For more information, see "About apps."
No canto superior direito de qualquer página, clique na foto do seu perfil e em Configurações.
In the left sidebar, click Developer settings.
In the left sidebar, click Personal access tokens.
Clique em Gerar novo token.
Give your token a descriptive name.
To give your token an expiration, select the Expiration drop-down menu, then click a default or use the calendar picker.
Select the scopes you'd like to grant this token. To use your token to access repositories from the command line, select repo. A token with no assigned scopes can only access public information. For more information, see "Available scopes".
Click Generate token.
Se você tem um token, é possível inseri-lo em vez de sua senha ao realizar operações Git em HTTPS.
Por exemplo, você digitaria o seguinte na linha de comando:
$ git clone https://hostname/username/repo.git Username: your_username Password: your_token
Personal access tokens can only be used for HTTPS Git operations. If your repository uses an SSH remote URL, you will need to switch the remote from SSH to HTTPS.
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 to replace your old password with the token.
Instead of manually entering your personal access token for every HTTPS Git operation, you can cache your personal access 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 GitHub credentials in Git."