| May | JUN | Jul |
| 27 | ||
| 2017 | 2018 | 2019 |
COLLECTED BY
Collection: Live Web Proxy Crawls
For information on setting or changing your remote URL, see "Changing a remote's URL."
https:// clone URLs are available on all repositories, public and private. These URLs work everywhere--even if you are behind a firewall or proxy. In certain cases, if you'd rather use SSH, you might be able to use SSH over the HTTPS port.
When you git clone, git fetch, git pull, or git push to a remote repository using HTTPS URLs on the command line, you'll be asked for your GitHub username and password.
If you have enabled two-factor authentication, or if you are accessing an organization that uses SAML single sign-on, you must provide a personal access token instead of entering your password for HTTPS Git.
Tips:
You can use a credential helper so Git will remember your GitHub username and password every time it talks to GitHub.
To clone a repository without authenticating to GitHub on the command line, you can use GitHub Desktop to clone instead.
git clone, git fetch, 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.
If you are accessing an organization that uses SAML single sign-on, you won't be able to clone with SSH. Instead, clone with the HTTPS URL.
Tip: SSH URLs can be used locally, 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.