According to Github's documentation,
>Once you have a personal access token, you can enter it instead of your password when performing Git operations over HTTPS.
>
>For example, to clone a repository on the command line you would enter the following git clone command. You would then be prompted to enter your username and password. When prompted for your password, enter your personal access token instead of a password.
>
>`$ git clone https://github.com/USERNAME/REPO.git
 Username: YOUR_USERNAME
Password: YOUR_PERSONAL_ACCESS_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.](https://docs.github.com/en/get-started/getting-started-with-git/caching-your-github-credentials-in-git)"

In summary, it looks like you just need to use a git command that attempts to establish contact with a secure server, and the terminal will prompt for your login info.
spam fails_task lang_mismatch pii not_appropriate hate_speech sexual_content quality toxicity humor helpfulness creativity violence