When you view a repository while signed in to your account, the URLs you can use to clone the project onto your computer are available below the repository details:
For information on setting or changing your remote URL, see "Changing a remote's URL."
https:// clone URLs are available on all repositories, regardless of visibility.
https:// clone URLs work even if you are behind a firewall or proxy.
git pull, or
git push to a remote repository using HTTPS URLs on the command line, Git will ask for your GitHub AE username and password. When Git prompts you for your password, enter your personal access token (PAT) instead. For more information, see "Creating a personal access token."
You can use a credential helper so Git will remember your GitHub credentials every time it talks to GitHub. For more information, see "Caching your GitHub credentials in Git."
To clone a repository without authenticating to GitHub AE on the command line, you can use GitHub Desktop to clone instead. For more information, see "Cloning a repository from GitHub to GitHub Desktop."
SSH URLs provide access to a Git repository via SSH, a secure protocol. To use these URLs, you must generate an SSH keypair on your computer and add the public key to your GitHub AE account. For more information, see "Connecting to GitHub with SSH."
git pull, or
git push to a remote repository using SSH URLs, you'll be prompted for a password and must provide your SSH key passphrase. For more information, see "Working with SSH key passphrases."
Tip: You can use an SSH URL to clone a repository to your computer, or as a secure way of deploying your code to production servers. You can also use SSH agent forwarding with your deploy script to avoid managing keys on the server. For more information, see "Using SSH Agent Forwarding."
You can also install GitHub CLI to use GitHub AE workflows in your terminal. For more information, the GitHub CLI documentation.
- Working with Remotes from the Pro Git book site