Handling a remote rename/move with Git

I recently had to rename a repo on my Github account. Github has made this very easy but it's just one side of the issue. Obviously you must also update any references to this remote in other clones, otherwise pushes, fetches etc won't work anymore.

You can do this in two ways:

  • open .git/config and modify the url for the remote manually
  • git remote rm origin && git remote add origin git@github.com:$user/$project.git

That's it! All will work fine again.

Trackback URL for this post:

http://dieter.plaetinck.be/trackback/55
Submitted by Dieter_be on Mon, 11/17/2008 - 12:29. categories [ ]

Very interesting article.

Submitted by bilety lotnicze (not verified) on Sat, 01/17/2009 - 13:37.

Very interesting article. Thanks

it works ! thanks dude

Submitted by sts (not verified) on Tue, 10/06/2009 - 00:19.

it works ! thanks dude

Keep up the good work, and

Submitted by jesse (not verified) on Tue, 10/20/2009 - 04:36.

Keep up the good work, and post more articles like the one you have posted above.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Web page addresses and e-mail addresses turn into links automatically.
  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.
  • You can enable syntax highlighting of source code with the following tags: <code>, <blockcode>. Beside the tag style "<foo>" it is also possible to use "[foo]". PHP source code can also be enclosed in <?php ... ?> or <% ... %>.

More information about formatting options

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.
Security question, designed to stop automated spam bots