Frecuentemente publicamos actualizaciones de nuestra documentación. Es posible que la traducción de esta página esté en curso. Para conocer la información más actual, visita la documentación en inglés. Si existe un problema con las traducciones en esta página, por favor infórmanos.
GitHub AE is currently under limited release. Please contact our Sales Team to find out more.

Which remote URL should I use?

There are several ways to clone repositories available on tu instancia de servidor de GitHub Enterprise.

En este artículo

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."

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 Enterprise 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".

Tips:

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 Enterprise 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."

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 Enterprise workflows in your terminal. For more information, the CLI de GitHub documentation.

Further reading

¿Te ayudó este documento?

Privacy policy

Help us make these docs great!

All GitHub docs are open source. See something that's wrong or unclear? Submit a pull request.

Make a contribution

O, learn how to contribute.