6450

I have a repo (origin) on a USB key that I cloned on my hard drive (local). I moved "origin" to a NAS and successfully tested cloning it from here.

I would like to know if I can change the URI of "origin" in the settings of "local" so it will now pull from the NAS, and not from the USB key.

For now, I can see two solutions:

  • push everything to the USB origin, and copy it to the NAS again (implies a lot of work due to new commits to NAS origin);

  • add a new remote to "local" and delete the old one (I fear I'll break my history).

4
  • 9
    I had to do this on an old version of git (1.5.6.5) and the set-url option did not exist. Simply deleting the unwanted remote and adding a new one with the same name worked without problem and maintained history just fine.
    – HotN
    Commented Sep 11, 2014 at 21:17
  • in my case i need to check my permission i have two private git repositories and this second account is admin of that new repo and first one is my default user account and i should grant permission to first Commented Feb 6, 2020 at 16:35
  • Nice Doc is available here. docs.github.com/en/free-pro-team@latest/github/using-git/… Commented Dec 28, 2020 at 8:49
  • The answers here show the easiest way to clone a remote repo locally (if the web console does not allow it, like in on-premise Bitbucket, where the import feature is flawed - you cannot clone existing repo under a new name in the same namespace).
    – mirekphd
    Commented Aug 7, 2022 at 11:32

34 Answers 34

10308

You can

git remote set-url origin new.git.url/here

See git help remote. You also can edit .git/config and change the URLs there.

You're not in any danger of losing history unless you do something very silly (and if you're worried, just make a copy of your repo, since your repo is your history.)

19
  • 43
    If you have a different shell user then maybe you want to specify your git user in the beginning of the new url e.g.: myself@git://new.url.here
    – sobi3ch
    Commented Jul 1, 2013 at 7:49
  • 22
    You may also want to set the master upstream branch for your new origin location with: git branch -u origin/master. This will allow you to just git push instead of having to git push origin master every time.
    – kelorek
    Commented Aug 13, 2013 at 18:06
  • 43
    @kelorek or you can just git push -u origin master the first time :)
    – hobbs
    Commented Aug 14, 2013 at 19:38
  • 55
    I also had to git remote set-url --push origin git://... in order to set the origin ... (push) url.
    – jpillora
    Commented Jun 2, 2014 at 9:12
  • 12
    For multiple branches, you can use git push -u --all to push all branches at once to new url (instead of git push -u origin master)
    – Ben
    Commented Jan 14, 2018 at 16:11
1846
git remote -v
# View existing remotes
# origin  https://github.com/user/repo.git (fetch)
# origin  https://github.com/user/repo.git (push)

git remote set-url origin https://github.com/user/repo2.git
# Change the 'origin' remote's URL

git remote -v
# Verify new remote URL
# origin  https://github.com/user/repo2.git (fetch)
# origin  https://github.com/user/repo2.git (push)

Changing a remote's URL

6
  • 4
    To get them all, I added: git remote set-url --push origin [email protected]/User/Branch.git and git remote set-url composer https://github.com/User/Branch.git
    – Reed
    Commented Jul 14, 2020 at 18:56
  • 57
    @MS Berends The git remote -v helped for verification, whereas the accepted solution did not provide that.
    – rmutalik
    Commented Nov 10, 2020 at 18:49
  • Note: if you're getting 403 forbidden, follow this tutorial: janac.medium.com/… Commented Sep 8, 2021 at 18:10
  • I did this, but after I did push with git add . && git commit -m 'fix' && git push origin to the new remote and it says everything is up-to-date while the new remote is empty. What could be the reason ?
    – Florent
    Commented Jul 15, 2022 at 9:14
  • 1
    I like that this shows before and after with git remote -v
    – mike
    Commented May 25 at 23:52
143

Change Host for a Git Origin Server

from: http://pseudofish.com/blog/2010/06/28/change-host-for-a-git-origin-server/

Hopefully this isn’t something you need to do. The server that I’ve been using to collaborate on a few git projects with had the domain name expire. This meant finding a way of migrating the local repositories to get back in sync.

Update: Thanks to @mawolf for pointing out there is an easy way with recent git versions (post Feb, 2010):

git remote set-url origin ssh://newhost.com/usr/local/gitroot/myproject.git

See the man page for details.

If you’re on an older version, then try this:

As a caveat, this works only as it is the same server, just with different names.

Assuming that the new hostname is newhost.com, and the old one was oldhost.com, the change is quite simple.

Edit the .git/config file in your working directory. You should see something like:

[remote "origin"]
fetch = +refs/heads/*:refs/remotes/origin/*
url = ssh://oldhost.com/usr/local/gitroot/myproject.git

Change oldhost.com to newhost.com, save the file and you’re done.

From my limited testing (git pull origin; git push origin; gitx) everything seems in order. And yes, I know it is bad form to mess with git internals.

3
  • Bad form? Perhaps. But if you need to do something the authors didn't expect anyone would ever need to do, then sometimes messing with the internals is required. But you do have to be willing to accept the consequences if you get it wrong. Backup your local repository _before_ messing with git internals. Commented Oct 20, 2016 at 15:41
  • where I can find .git/config Commented Oct 8, 2020 at 15:36
  • The pseudofish blog entry has moved and is now located at pseudofish.com/change-host-for-a-git-origin-server.html
    – DDay
    Commented Mar 29, 2023 at 16:01
119

This is very easy and simple; just follow these instructions.

  1. For adding or changing the remote origin:
    git remote set-url origin githubrepurl
    
  2. To see which remote URL you have currently in this local repository:
    git remote show origin
    
1
  • what if it shows fatal: 'origin' does not appear to be a git repository Commented May 16, 2022 at 18:22
90

Switching remote URLs

Open Terminal.

Ist Step:- Change the current working directory to your local project.

2nd Step:- 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.

3rd Step:- git remote set-url origin [email protected]:USERNAME/REPOSITORY.git

4th Step:- Now Verify that the remote URL has changed.

git remote -v Verify new remote URL

origin  [email protected]:USERNAME/REPOSITORY.git (fetch)
origin  [email protected]:USERNAME/REPOSITORY.git (push)
2
  • Do you have to remove the old origin before you add the new origin?
    – Sledge
    Commented Feb 27, 2019 at 20:17
  • I didn't remove from the project anything. I simply do the above steps and it worked Commented Feb 28, 2019 at 7:56
84
git remote set-url origin git://new.location

(alternatively, open .git/config, look for [remote "origin"], and edit the url = line.

You can check it worked by examining the remotes:

git remote -v
# origin  git://new.location (fetch)
# origin  git://new.location (push)

Next time you push, you'll have to specify the new upstream branch, e.g.:

git push -u origin master

See also: GitHub: Changing a remote's URL

2
  • I could not set the new origin by editing .git/config. It said the git repository named in the URL wasn't a git repository. Once I removed and re-created origin, all was well. I had not looked up git remote set-url as a solution to my problem, though. Commented Sep 15, 2015 at 13:55
  • 4
    +1 for providing a complete answer with the git push -u command. Maybe obvious to others, wasn't for me.
    – testphreak
    Commented Sep 20, 2019 at 21:51
68

As seen here,

$ git remote rm origin
$ git remote add origin [email protected]:aplikacjainfo/proj1.git
$ git config master.remote origin
$ git config master.merge refs/heads/master
3
  • 26
    When adding an answer to a ten year old question with twenty one other answers it is really important to include an explanation of your answer and to point out what new aspect of the question your answer addresses. With answers that are a series of commands it is useful to explain what each is doing and how to undo the effects of each of them if that is possible. The undo is important in case someone is able to perform the first few steps, but then encounters an error on a later step. Commented Apr 2, 2020 at 16:01
  • 8
    @JasonAller I think this is fairly self-explanatory though and it's the best answer here by far, the others are a joke. Commented May 13, 2020 at 13:07
  • this will also update git status Your branch is ahead of 'origin/master' by n commits to the new one Commented Oct 16, 2021 at 13:26
62

It will work fine, you can try this

For SSH:

command: git remote set-url origin <ssh_url>

example: git remote set-url origin [email protected]:username/rep_name.git

For HTTPS:

command: git remote set-url origin <https_url>

example: git remote set-url origin https://github.com/username/REPOSITORY.git

43
  1. remove origin using command on gitbash git remote rm origin
  2. And now add new Origin using gitbash git remote add origin (Copy HTTP URL from your project repository in bit bucket) done
3
  • This is really useful answer because without git remote rm origin git remembers details about the old origin.
    – mato
    Commented Dec 11, 2019 at 8:02
  • 1
    The above git remote rm origin resolves the issue of multiple remotes: issue where I was not able to set the remote url. remote.origin.url has multiple values fatal: could not set 'remote.origin.url'
    – bitsand
    Commented Dec 26, 2019 at 15:47
  • @mato like what details?
    – minseong
    Commented Feb 23, 2022 at 22:54
42

First you need to type this command to view existing remotes

git remote -v

Then second you need to type this command to Change the 'origin' remote's URL

git remote set-url origin <paste your GitHub URL>

38

Change remote git URI to [email protected] rather than https://github.com

git remote set-url origin [email protected]:<username>/<repo>.git

Example:

git remote set-url origin [email protected]:Chetabahana/my_repo_name.git

The benefit is that you may do git push automatically when you use ssh-agent :

#!/bin/bash

# Check ssh connection
ssh-add -l &>/dev/null
[[ "$?" == 2 ]] && eval `ssh-agent`
ssh-add -l &>/dev/null
[[ "$?" == 1 ]] && expect $HOME/.ssh/agent

# Send git commands to push
git add . && git commit -m "your commit" && git push -u origin master

Put a script file $HOME/.ssh/agent to let it runs ssh-add using expect as below:

#!/usr/bin/expect -f
set HOME $env(HOME)
spawn ssh-add $HOME/.ssh/id_rsa
expect "Enter passphrase for $HOME/.ssh/id_rsa:"
send "<my_passphrase>\n";
expect "Identity added: $HOME/.ssh/id_rsa ($HOME/.ssh/id_rsa)"
interact
35

Write the below command from your repo terminal:

git remote set-url origin [email protected]:<username>/<repo>.git

Refer this link for more details about changing the url in the remote.

0
31

To check git remote connection:

git remote -v

Now, set the local repository to remote git:

git remote set-url origin https://NewRepoLink.git

Now to make it upstream or push use following code:

git push --set-upstream origin master -f

1
  • 1
    I was pushing and yet github didn't show my new branch. That last --set-upstream made it work.
    – OoDeLally
    Commented Jan 28, 2019 at 12:58
27

if you cloned your local will automatically consist,

remote URL where it gets cloned.

you can check it using git remote -v

if you want to made change in it,

git remote set-url origin https://github.io/my_repo.git

here,

origin - your branch

if you want to overwrite existing branch you can still use it.. it will override your existing ... it will do,

git remote remove url
and 
git remote add origin url

for you...

1
  • 1
    I had multiple remotes added, so git remote rm origin command was needed for removing all the associated urls. Then the add command worked.
    – bitsand
    Commented Dec 26, 2019 at 15:44
27

enter image description here

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.

Reference : https://help.github.com/articles/changing-a-remote-s-url/

27

Navigate to the project root of the local repository and check for existing remotes:

git remote -v

If your repository is using SSH you will see something like:

> origin  [email protected]:USERNAME/REPOSITORY.git (fetch)
> origin  [email protected]:USERNAME/REPOSITORY.git (push)

And if your repository is using HTTPS you will see something like:

> origin  https://github.com/USERNAME/REPOSITORY.git (fetch)
> origin  https://github.com/USERNAME/REPOSITORY.git (push)

Changing the URL is done with git remote set-url. Depending on the output of git remote -v, you can change the URL in the following manner:

In case of SSH, you can change the URL from REPOSITORY.git to NEW_REPOSITORY.git like:

$ git remote set-url origin [email protected]:USERNAME/NEW_REPOSITORY.git

And in case of HTTPS, you can change the URL from REPOSITORY.git to NEW_REPOSITORY.git like:

$ git remote set-url origin https://github.com/USERNAME/NEW_REPOSITORY.git

NOTE: If you've changed your GitHub username, you can follow the same process as above to update the change in the username associated with your repository. You would only have to update the USERNAME in the git remote set-url command.

27

If you would like to set the username and password as well in the origin url, you can follow the below steps.

Exporting the password in a variable would avoid issues with special characters.

Steps:

export gituser='<Username>:<password>@'
git remote set-url origin https://${gituser}<gitlab_repo_url> 
git push origin <Branch Name>
25

I worked:

git remote set-url origin <project>
24

For me, the accepted answer worked only in the case of fetch but not pull. I did the following to make it work for push as well.

git remote set-url --push origin new.git.url/here

So to update the fetch URL:

git remote set-url origin new.git.url/here

To update the pull URL:

git remote set-url --push origin new.git.url/here
22

In the Git Bash, enter the command:

git remote set-url origin https://NewRepoLink.git

Enter the Credentials

Done

22

You have a lot of ways to do that:

Console

git remote set-url origin [Here new url] 

Just be sure that you've opened it in a place where a repository is.

Config

It is placed in .git/config (same folder as repository)

[core]
    repositoryformatversion = 0
    filemode = false
    bare = false
    logallrefupdates = true
    symlinks = false
    ignorecase = true
[remote "origin"]
    url = [Here new url]  <------------------------------------
...

TortoiseGit

Step 1 - open settings

Step 2 - change url

Then just edit URL.

SourceTree

  1. Click on the "Settings" button on the toolbar to open the Repository Settings window.

  2. Click "Add" to add a remote repository path to the repository. A "Remote details" window will open.

  3. Enter a name for the remote path.

  4. Enter the URL/Path for the remote repository

  5. Enter the username for the hosting service for the remote repository.

  6. Click 'OK' to add the remote path.

  7. Back on the Repository Settings window, click 'OK'. The new remote path should be added on the repository now.

  8. If you need to edit an already added remote path, just click the 'Edit' button. You should be directed to the "Remote details" window where you can edit the details (URL/Path/Host Type) of the remote path.

  9. To remove a remote repository path, click the 'Remove' button

enter image description here

enter image description here

ref. Support

18

To change the remote upstream: git remote set-url origin <url>


To add more upstreams: git remote add newplace <url>

So you can choose where to work git push origin <branch> or git push newplace <branch>

0
17

Go to the folder/repo where you want to change and execute the below commands:

The below command will change the git fetch url of the repo.

git remote set-url origin <your new url>.git

The below command will change the git push url of the repo.

git remote set-url --push origin <your new url>.git

The below command to check whether the above changes reflected or not

git remote -v
15

An alternative approach is to rename the 'old' origin (in the example below I name it simply old-origin) and adding a new one. This might be the desired approach if you still want to be able to push to the old origin every now and then:

git remote rename origin old-origin
git remote add origin [email protected]>:<username>/<projectname>.git

And in case you need to push your local state to the new origin:

git push -u origin --all
git push -u origin --tags
15

Removing a remote

Use the git remote rm command to remove a remote URL from your repository.

$ git remote -v
# View current remotes
> origin  https://github.com/OWNER/REPOSITORY.git (fetch)
> origin  https://github.com/OWNER/REPOSITORY.git (push)
> destination  https://github.com/FORKER/REPOSITORY.git (fetch)
> destination  https://github.com/FORKER/REPOSITORY.git (push)

$ git remote rm destination
# Remove remote
$ git remote -v
# Verify it's gone
> origin  https://github.com/OWNER/REPOSITORY.git (fetch)
> origin  https://github.com/OWNER/REPOSITORY.git (push)
14

You can change the url by editing the config file. Go to your project root:

nano .git/config

Then edit the url field and set your new url. Save the changes. You can verify the changes by using the command.

git remote -v 
12

If you're using TortoiseGit then follow the below steps:

  1. Go to your local checkout folder and right click to go to TortoiseGit -> Settings
  2. In the left pane choose Git -> Remote
  3. In the right pane choose origin
  4. Now change the URL text box value to where ever your new remote repository is

Your branch and all your local commits will remain intact and you can keep working as you were before.

0
6

check your privilege

in my case i need to check my username

i have two or three repository with seperate credentials.

problem is my permission i have two private git server and repositories

this second account is admin of that new repo and first one is my default user account and i should grant permission to first

6

This answer pertains to a question I wasn't able to find an answer for elsewhere: doing this for a project in Gitlab, which has a subgroup. This did work via SSH:

git remote add origin [email protected]:group/subgroup/project.git

In contrast to all the answers which have "username" instead of "group", none of those worked for me via SSH. Alternatively, what worked through https:

git remote add origin https://[email protected]/group/subgroup/project.git

Do note the difference in the two with ".com:group" and ".com/group"

If this doesn't work right out of the box, I used the HTTPS method before successfully using the SSH one, might be a factor but I can't be arsed to try and replicate it without it.

1
  • Thank you, I downloaded repo from zip file instead of cloning it, using git remote set-url does not work, only with add was possible to sync files. Commented May 31, 2023 at 12:36
5

(Only Windows PS) To change a server/protocol recursively in all local repos

Get-ChildItem -Directory -Recurse -Depth [Number] -Hidden -name | %{$_.replace("\.git","")} | %{git -C $_ remote set-url origin $(git -C $_ remote get-url origin).replace("[OLD SERVER]", "[NEW SERVER]")}

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.