About remote repositories

GitHub's collaborative approach to development depends on publishing commits from your local repository to GitHub for other people to view, fetch, and update.

이 문서의 내용

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 git@github.com: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 private remote repository using HTTPS URLs on the command line, Git will ask for your GitHub username and password. Git에서 암호를 입력하라는 메시지가 표시되면 personal access token을(를) 입력합니다. 또는 Git 자격 증명 관리자와 같은 자격 증명 도우미를 사용할 수 있습니다. 보다 안전한 인증 방법을 지원하기 위해 Git에서 암호 기반 인증이 제거되었습니다. 자세한 내용은 개인용 액세스 토큰 관리을(를) 참조하세요.

SAML SSO를 사용하는 조직에 액세스하고 personal access token (classic)을 사용하는 경우 인증하기 전에 personal access token에 액세스할 수 있도록 권한을 부여해야 합니다. 자세한 내용은 SAML Single Sign-On을 사용한 인증 정보 및 SAML Single Sign-On에 사용할 개인용 액세스 토큰 권한 부여을(를) 참조하세요.

Tip

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 HTTPS 포트를 통해 SSH 사용.

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 account on GitHub. For more information, see SSH를 통한 GitHub 연결.

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 SSH 키 암호 사용.

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 SAML Single Sign-On을 사용한 인증 정보 and SAML Single Sign-On에 사용할 SSH 키 권한 부여" in the GitHub Enterprise Cloud documentation.

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 SSH 에이전트 전달 사용.

Cloning with GitHub CLI

You can also install GitHub CLI to use GitHub workflows in your terminal. For more information, see GitHub CLI 정보.