- Open Terminal (for Mac and Linux users) or the command prompt (for Windows users).
- Change the current working directory to your local project.
-
List your existing remotes in order to get the name of the remote you want to change.
git remote -v
origin git@github.com:USERNAME/REPOSITORY.git (fetch)
origin git@github.com:USERNAME/REPOSITORY.git (push)
-
Change your remote's URL from SSH to HTTPS with the
git remote set-url
command.
git remote set-url origin https://github.com/USERNAME/OTHERREPOSITORY.git
-
Verify that the remote URL has changed.
git remote -v
origin https://github.com/USERNAME/OTHERREPOSITORY.git (fetch)
origin https://github.com/USERNAME/OTHERREPOSITORY.git (push)
The next time you
git fetch
,
git pull
, or
git push
to the remote repository, you'll be asked for your GitHub username and password.
Switching remote URLs from HTTPS to SSH
- Open Terminal (for Mac and Linux users) or the command prompt (for Windows users).
- Change the current working directory to your local project.
-
List your existing remotes in order to get the name of the remote you want to change.
git remote -v
origin https://github.com/USERNAME/REPOSITORY.git (fetch)
origin https://github.com/USERNAME/REPOSITORY.git (push)
-
Change your remote's URL from HTTPS to SSH with the
git remote set-url
command.
git remote set-url origin git@github.com:USERNAME/OTHERREPOSITORY.git
-
Verify that the remote URL has changed.
git remote -v
origin git@github.com:USERNAME/OTHERREPOSITORY.git (fetch)
origin git@github.com:USERNAME/OTHERREPOSITORY.git (push)
Troubleshooting
You may encounter these errors when trying to changing a remote.
No such remote '[name]'
This error means that the remote you tried to change doesn't exist:
git remote set-url sofake https://github.com/octocat/Spoon-Knife
fatal: No such remote 'sofake'
Check that you've correctly typed the remote name.
No comments:
Post a Comment