Moving git repository and all its branches, tags to a new remote repository keeping commits history

git.migrate

#!/bin/bash
# Sometimes you need to move your existing git repository
# to a new remote repository (/new remote origin).
# Here are a simple and quick steps that does exactly this.
#
# Let's assume we call "old repo" the repository you wish
# to move, and "new repo" the one you wish to move to.
#
### Step 1. Make sure you have a local copy of all "old repo"
### branches and tags.
# Fetch all of the remote branches and tags:
git fetch origin

# View all "old repo" local and remote branches:
git branch -a

# If some of the remotes/ branches doesn't have a local copy,
# checkout to create a local copy of the missing ones:
git checkout -b <branch> origin/<branch>

# Now we have to have all remote branches locally.


### Step 2. Add a "new repo" as a new remote origin:
git remote add new-origin [email protected]:user/repo.git


### Step 3. Push all local branches and tags to a "new repo".
# Push all local branches (note we're pushing to new-origin):
git push --all new-origin

# Push all tags:
git push --tags new-origin


### Step 4. Remove "old repo" origin and its dependencies.
# View existing remotes (you'll see 2 remotes for both fetch and push)
git remote -v

# Remove "old repo" remote:
git remote rm origin

# Rename "new repo" remote into just 'origin':
git remote rename new-origin origin


### Done! Now your local git repo is connected to "new repo" remote
### which has all the branches, tags and commits history.

Hi, i didnt createany new branch. I migrated old existing branches to the new repo. All branches except default are treated as new branches and thus asking for pull request. how do i migrate smoothly without asking for pull requests.?

…

On Thu, Sep 26, 2019 at 12:16 PM Nik Sumeiko ***@***.***> wrote: @ ravindrabhandarkar007, your branches are new, because they were migrated from an old repository and pushed along with the rest. If you keep working on your main branches, these won't popup for pull request anymore. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <https://gist.github.com/8972566?email_source=notifications&email_token=ALIO4IHG6XG7Q4OUOSMWFOTQLRLDJA5CNFSM4HW7NI3KYY3PNVWWK3TUL52HS4DFVNDWS43UINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAFZNNM#gistcomment-3037910>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALIO4IFBGPNGUXMRQJRBMG3QLRLDJANCNFSM4HW7NI3A> .

When you migrate, you push everything from your local to a new repository (new "remote" in git terms). Old branches are considered new by a new remote because they were pushed for a first time.

cant we prevent that scenario. cant we prevent it from happening? I want them to be treated as old branches only.help me out?

…

On Thu, Sep 26, 2019 at 1:35 PM Nik Sumeiko ***@***.***> wrote: When you migrate, you push everything from your local to a new repository (new "remote" in git terms). Old branches are considered new by a new remote because they were pushed for a first time. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://gist.github.com/8972566?email_source=notifications&email_token=ALIO4IDZPNVQONIOYJYUJ4TQLRUOBA5CNFSM4HW7NI3KYY3PNVWWK3TUL52HS4DFVNDWS43UINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAFZNRU#gistcomment-3037978>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALIO4IENPGLSBY2DMW6NOKDQLRUOBANCNFSM4HW7NI3A> .

Can we fork it? is it a good practice? is there any other way? On Fri, Sep 27, 2019 at 11:49 AM ravindra bhandarkar < [email protected]> wrote:

…

cant we prevent that scenario. cant we prevent it from happening? I want them to be treated as old branches only.help me out? On Thu, Sep 26, 2019 at 1:35 PM Nik Sumeiko ***@***.***> wrote: > When you migrate, you push everything from your local to a new repository > (new "remote" in git terms). Old branches are considered new by a new > remote because they were pushed for a first time. > > — > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub > <https://gist.github.com/8972566?email_source=notifications&email_token=ALIO4IDZPNVQONIOYJYUJ4TQLRUOBA5CNFSM4HW7NI3KYY3PNVWWK3TUL52HS4DFVNDWS43UINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAFZNRU#gistcomment-3037978>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ALIO4IENPGLSBY2DMW6NOKDQLRUOBANCNFSM4HW7NI3A> > . >

waiting for your reply On Fri, Sep 27, 2019 at 12:00 PM ravindra bhandarkar < [email protected]> wrote:

…

Can we fork it? is it a good practice? is there any other way? On Fri, Sep 27, 2019 at 11:49 AM ravindra bhandarkar < ***@***.***> wrote: > cant we prevent that scenario. cant we prevent it from happening? > I want them to be treated as old branches only.help me out? > > On Thu, Sep 26, 2019 at 1:35 PM Nik Sumeiko ***@***.***> > wrote: > >> When you migrate, you push everything from your local to a new >> repository (new "remote" in git terms). Old branches are considered new by >> a new remote because they were pushed for a first time. >> >> — >> You are receiving this because you were mentioned. >> Reply to this email directly, view it on GitHub >> <https://gist.github.com/8972566?email_source=notifications&email_token=ALIO4IDZPNVQONIOYJYUJ4TQLRUOBA5CNFSM4HW7NI3KYY3PNVWWK3TUL52HS4DFVNDWS43UINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAFZNRU#gistcomment-3037978>, >> or mute the thread >> <https://github.com/notifications/unsubscribe-auth/ALIO4IENPGLSBY2DMW6NOKDQLRUOBANCNFSM4HW7NI3A> >> . >> >

waiting for your reply On Fri, Sep 27, 2019 at 12:00 PM ravindra bhandarkar < [email protected]> wrote:
…
Can we fork it? is it a good practice? is there any other way? On Fri, Sep 27, 2019 at 11:49 AM ravindra bhandarkar < @.> wrote: > cant we prevent that scenario. cant we prevent it from happening? > I want them to be treated as old branches only.help me out? > > On Thu, Sep 26, 2019 at 1:35 PM Nik Sumeiko @.> > wrote: > >> When you migrate, you push everything from your local to a new >> repository (new "remote" in git terms). Old branches are considered new by >> a new remote because they were pushed for a first time. >> >> — >> You are receiving this because you were mentioned. >> Reply to this email directly, view it on GitHub >> https://gist.github.com/8972566?email_source=notifications&email_token=ALIO4IDZPNVQONIOYJYUJ4TQLRUOBA5CNFSM4HW7NI3KYY3PNVWWK3TUL52HS4DFVNDWS43UINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAFZNRU#gistcomment-3037978, >> or mute the thread >> https://github.com/notifications/unsubscribe-auth/ALIO4IENPGLSBY2DMW6NOKDQLRUOBANCNFSM4HW7NI3A >> . >> >

if you want to migrate the reponsitory. you must use --bare or --mirror option to clone it. then push it to the new remote reponsitory. Then all the branches will be migrate to the new repnsitory.

Doesn't matter how we migrate, as soon as we push old branches to a new remote they will be considered as new once and Github will offer creating pull requests out them. But this Github notification is private to an author, so no one else sees them. As well, they will disappear when you keep working/pushing to your main branches within time. @ravindrabhandarkar007, why are you worrying?

waiting for your reply

…

On Mon, Sep 30, 2019 at 3:40 PM liyongjun1 ***@***.***> wrote: waiting for your reply On Fri, Sep 27, 2019 at 12:00 PM ravindra bhandarkar < ***@***.***> wrote: … <#m_-4870128654150935762_> Can we fork it? is it a good practice? is there any other way? On Fri, Sep 27, 2019 at 11:49 AM ravindra bhandarkar < *@*.*> wrote: > cant we prevent that scenario. cant we prevent it from happening? > I want them to be treated as old branches only.help me out? > > On Thu, Sep 26, 2019 at 1:35 PM Nik Sumeiko @.*> > wrote: > >> When you migrate, you push everything from your local to a new >> repository (new "remote" in git terms). Old branches are considered new by >> a new remote because they were pushed for a first time. >> >> — >> You are receiving this because you were mentioned. >> Reply to this email directly, view it on GitHub >> https://gist.github.com/8972566?email_source=notifications&email_token=ALIO4IDZPNVQONIOYJYUJ4TQLRUOBA5CNFSM4HW7NI3KYY3PNVWWK3TUL52HS4DFVNDWS43UINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAFZNRU#gistcomment-3037978, >> or mute the thread >> https://github.com/notifications/unsubscribe-auth/ALIO4IENPGLSBY2DMW6NOKDQLRUOBANCNFSM4HW7NI3A >> . >> > if you want to migrate the reponsitory. you must use --bare or --mirror option to clone it. then push it to the new remote reponsitory. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://gist.github.com/8972566?email_source=notifications&email_token=ALIO4IBDOCG3BMZFCUY3C63QMHGARA5CNFSM4HW7NI3KYY3PNVWWK3TUL52HS4DFVNDWS43UINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAFZTNO#gistcomment-3040983>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALIO4IDKENPH5JHPTSEMIFTQMHGARANCNFSM4HW7NI3A> .

git push new-origin --mirror

When i run command in Git bash, It is giving error you are exceeded the Git hub limit.
Git supports 100 MB while pushing the commits/Repo but my cloned existing Repo size is 350 MB.
How can we achieve this?

Steps executed:

1. I have Cloned one repository from Gitlab eg: Repo1
2. cd " Repo1"
3. git add origin "Repo2"(which is created in github not gitlab)
4. git push new-origin(Repo2) --mirror

Above mentioned error occurs and i could't push the cloned Repo1 to new Repo2 which is created in git hub.

what is the error you are getting. Could you please send a screenshot?

…

On Fri, Oct 18, 2019 at 6:51 PM ganginenivenu ***@***.***> wrote: git push new-origin --mirror When i run command in Git bash, It is giving error you are exceeded the Git hub limit. Git supports 100 MB while pushing the commits/Repo but my cloned existing Repo size is 350 MB. How can we achieve this? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://gist.github.com/8972566?email_source=notifications&email_token=ALIO4IE32PWTHORXUTIIKV3QPGZ65A5CNFSM4HW7NI3KYY3PNVWWK3TUL52HS4DFVNDWS43UINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAF2XCC#gistcomment-3059233>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALIO4IGPHXYSPZ7EYF4KL23QPGZ65ANCNFSM4HW7NI3A> .

1. git clone <repo-a-url> tmp-repo 2. cd tmp-repo 3. git checkout <branch-in-repo-a> 4. git remote rm origin # not really needed 5. git filter-branch --subdirectory-filter <directory-to-move> -- --all 6. mkdir -p <target-path in="" repo-b=""> 7. git mv -k * <target-path in="" repo-b=""> 8. git commit 9. cd <path-to-local-repo-b> # clone it, if you didn't do already 10. Create a new branch and check it out 11. git remote add origin-tmp-repo <path to="" tmp-repo=""> 12. git pull origin-tmp-repo <branch-in-repo-a> 13. rm -rf <path to="" tmp-repo="">

…

On Fri, Oct 18, 2019 at 8:05 PM ganginenivenu ***@***.***> wrote: [image: git erro] <https://user-images.githubusercontent.com/33112173/67103349-79b7b280-f1b4-11e9-8e5a-b59c8571163c.PNG> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://gist.github.com/8972566?email_source=notifications&email_token=ALIO4IHVIWXMYPKFM2DSSU3QPHCR3A5CNFSM4HW7NI3KYY3PNVWWK3TUL52HS4DFVNDWS43UINXW23LFNZ2KUY3PNVWWK3TUL5UWJTQAF2XGM#gistcomment-3059302>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALIO4IAWPEXNT4LUY2B4SWTQPHCR3ANCNFSM4HW7NI3A> .

Thanks @niksumeiko

git clone --bare {repo}
cd {project}.git
git push --mirror {new-repo}

@niksumeiko one question is that how would the other developers that already have existing git repo linked with the old repo URL ? how can they migrate their origin ?

@monil1334, other developers that already have an existing repo, shall only update their origin to a new url:

# Set a "new repo" url to remote origin:
git remote set-url [email protected]:user/repo.git

Now every developer can continue to pull/push as it used to be. A code will be retrieved and sent to a new repository.

git remote set-url origin <URL of git repo> git push

…

On Thu, May 7, 2020 at 11:23 AM Nik Sumeiko ***@***.***> wrote: ***@***.**** commented on this gist. ------------------------------ @monil1334 <https://github.com/monil1334>, other developers that already have an existing repo, shall only remove their current origin and add a new origin pointing to a new repository url: # Remove "old repo" remote: git remote rm origin # Add a "new repo" as a new remote origin, pointing to a new url: git remote add origin ***@***.***:user/repo.git Now every developer can continue to pull/push as it used to be. A code will be retrieved and sent to a new repository. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <https://gist.github.com/8972566#gistcomment-3293731>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALIO4ICRB45R6BINNUN6U7LRQJEGBANCNFSM4HW7NI3A> .

Thanks for the clear instructions!

if I already have a mirror pushed. and there are some updates to the original repository, will the same method update all the branches ?

Personally I think that it's much better to do it this way:

git clone --mirror URL
git remote add NEW-REMOTE URL
git push  NEW-REMOTE --mirror 

This works only if you have all commits pushed into the old repo. In my case, I was working on a public repo with some local commits and once I found it good, had to create a new repo of my own (but including my local commits and branches on top of the old repo). The sequence of steps mentioned by the OP helped me with that.

Works like a charm!

I want Transfer git repositories from Bonobo.Git.Server to GitHub

Than you so much

@niksumeiko Hi! I need to migrate from GH Enterprise to GH Enterprise Cloud. Is there a possibility to migrate all the closed Pull Requests as well? I can't find any GH REST API that helps(for obvious reasons I guess). Do you guys feel that if the code is merged and the base branches are already deleted why do we need to migrate those closed PR#s?

//Ashish

@niksumeiko Hi! I need to migrate from GH Enterprise to GH Enterprise Cloud. Is there a possibility to migrate all the closed Pull Requests as well? I can't find any GH REST API that helps(for obvious reasons I guess). Do you guys feel that if the code is merged and the base branches are already deleted why do we need to migrate those closed PR#s?

@astiw2, there's totally a way to do GH Enterprise migration (incl. all pull requests, issues…), but not via the git command line. Please consult with GH enterprise support people. They serve us wonderful. We're also on their Enterprise tyre.

Personally I think that it's much better to do it this way:

git clone --mirror URL
git remote add NEW-REMOTE URL
git push  NEW-REMOTE --mirror 

@prashathsenthil You have to run these commands as below

git clone --mirror <url_of_old_repo>
cd <name_of_old_repo>
git remote add new-origin <url_of_new_repo>
git push new-origin --mirror

Thanks very much, I do it in this way , migrate all the branches in the repository from gerrit to gitlab successfuuly.

can this work for Gitlab? I have a branch on a Company Gitlab project and I would like to see my contributions on my GitHub?

Is there a method to pull from git and migrate elsewhere such as svn for instance on a local repo with history? I've searched these internet pages a few months now and not much has come up.

git clone --bare {repo}
cd {project}.git
git push --mirror {new-repo}

This is the way.

Please no one do this. And unlike above comment, should use mirror the whole time.

git clone --mirror <URL to OLD repo location>
cd <New directory where OLD repo was cloned>
git remote set-url origin <URL to NEW repo location>
git push --mirror origin