About remote repositories
A remote URL is Git's fancy way of saying "the place where your code is stored." That URL could be your repository on GitHub, or another user's fork, or even on a completely different server.
You can only push to two types of URL addresses:
- An HTTPS URL like
https://github.com/user/repo.git - An SSH URL, like
[email protected]:user/repo.git
Git associates a remote URL with a name, and your default remote is usually called origin.
Creating remote repositories
You can use the git remote add command to match a remote URL with a name.
For example, you'd type the following in the command line:
git remote add origin <REMOTE_URL> This associates the name origin with the REMOTE_URL.
You can use the command git remote set-url to change a remote's URL.
Choosing a URL for your remote repository
There are several ways to clone repositories available on GitHub.
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 "Managing remote repositories."
Cloning with HTTPS URLs
The https:// clone URLs are available on all repositories, regardless of visibility. https:// clone URLs work even if you are behind a firewall or proxy.
When you git clone, git fetch, git pull, or git push to a remote repository using HTTPS URLs on the command line, Git will ask for your GitHub username and password. La autenticación basada en contraseña para Git es ahora obsoleta y te recomendamos utilizar un token de acceso personal (PAT) en sustitución cuando se te pida la contraseña, lo cual es más seguro. Trata a tu token tal como lo harías con una contraseña. Para obtener más información, consulta la sección "Crear un token de acceso personal".
Si estás accediendo a una organización que utiliza el SSO de SAML, también deberás autorizar tu token de acceso personal para ingresar a la organización antes de que te autentiques. Para obtener más información, consulta las secciónes "Acerca de la autenticación, con el inicio de sesión único de SAML" y "Autorizar un token de acceso personal para su uso con el inicio de sesión único de SAML".
Tips:
- 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 on the command line, you can use GitHub Desktop to clone instead. For more information, see "Cloning a repository from GitHub to GitHub Desktop."
If you'd rather use SSH but cannot connect over port 22, you might be able to use SSH over the HTTPS port. For more information, see "Using SSH over the HTTPS port."
Cloning with SSH URLs
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 account. For more information, see "Connecting to GitHub with SSH."
When you 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. For more information, see "Working with SSH key passphrases."
If you are accessing an organization that uses SAML single sign-on (SSO), you must authorize your SSH key to access the organization before you authenticate. For more information, see "About authentication with SAML single sign-on" and "Authorizing an SSH key for use with SAML single sign-on."
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."
Cloning with CLI de GitHub
You can also install CLI de GitHub to use GitHub workflows in your terminal. For more information, the CLI de GitHub documentation.
Cloning with Subversion
You can also use a Subversion client to access any repository on GitHub. Subversion offers a different feature set than Git. For more information, see "What are the differences between Subversion and Git?"
You can also access repositories on GitHub from Subversion clients. For more information, see "Support for Subversion clients."