Push local Git repo to new remote including all branches and tags

Question

I have a local Git repo that I would like to push to a new remote repo  brand new repo set up on Beanstalk  if that matters   My local repo has a few branches and tags  and I would like to keep all of my history     It looks like I basically just need to do a git push  but that only uploads the master branch     How do I push everything so I get a full replica of my local repo on the remote

User · Answer

In my case what worked was   git push origin --all

User · Answer

Mirroring a repository  Create a bare clone of the repository   git clone --bare https   github com exampleuser old-repository git   Mirror-push to the new repository   cd old-repository git git push --mirror https   github com exampleuser new-repository git   Remove the temporary local repository you created in step 1   cd    rm -rf old-repository git   Mirroring a repository that contains Git Large File Storage objects  Create a bare clone of the repository  Replace the example username with the name of the person or organization who owns the repository  and replace the example repository name with the name of the repository you d like to duplicate   git clone --bare https   github com exampleuser old-repository git   Navigate to the repository you just cloned   cd old-repository git   Pull in the repository s Git Large File Storage objects   git lfs fetch --all   Mirror-push to the new repository   git push --mirror https   github com exampleuser new-repository git   Push the repository s Git Large File Storage objects to your mirror   git lfs push --all https   github com exampleuser new-repository git   Remove the temporary local repository you created in step 1   cd    rm -rf old-repository git   Above instruction comes from Github Help  https   help github com articles duplicating-a-repository

User · Answer

To push branches and tags  but not remotes    git push origin  refs tags     refs heads      This would be equivalent to combining the --tags and --all options for git push  which git does not seem to allow

User · Answer

This is the most concise way I have found  provided the destination is empty  Switch to an empty folder and then     Note the period for cwd  gt  gt  gt  gt  gt  gt  gt  gt  gt  gt  gt  gt  gt  gt  gt  gt  gt  gt  gt  gt  gt  gt  gt  gt  v git clone --bare https   your-source-repo repo git   git push --mirror https   your-destination-repo repo git   Substitute https       for file    your repo etc  as appropriate

User · Answer

Below command will push all the branches including the ones which you have never checked-out but present in your git repo  you can see them by git branch -a   git push origin           NOTE  This command comes handy when you are migrating version control   service i e migrating from Gitlab to GitHub

User · Answer

The manpage for git-push is worth a read  Combined with this website I wrote the following in my  git config    remote  origin       url           fetch           push         push   refs tags     The push     means  push any  matching  branches  i e  branches that already exist in the remote repository and have a local counterpart    while push   refs tags   means  push all tags    So now I only have to run git push to push all matching branches and all tags   Yes  this is not quite what the OP wanted  all of the branches to push must already exist on the remote side   but might be helpful for those who find this question while googling for  how do I push branches and tags at the same time

User · Answer

Every time I Google how to do this I end up reading this same thread  but it doesn t get me where I need to be  so hopefully this will help my future self and others too  I started a new local project that I want to push to my repo  BitBucket   Here is what I did   navigate to my local project root initiate with  git init add all files with  git add   commit with  git commit -m  quot Initial commit quot  go to my repo  BitBucket  create new repository  new project go back to my local project add the remote with  git remote add origin git bitbucket org AndrewFox new project git push the commit with  git push origin master -f  The -f flag is to force the push  otherwise it will identify that the two repo s are different and fail

User · Answer

I found above answers still have some unclear things  which will mislead users  First  It s sure that git push new origin --all and git push new origin --mirror can t duplicate all branches of origin  it just duplicate your local existed branches to your new origin   Below is two useful methods I have tested   1 duplicate by clone bare repo git clone --bare origin url  then enter the folder  and git push new origin url --mirror By this way  you can also use git clone --mirror origin url  both --bareand --mirror will download a bare repo not including workspace  please refer this  2 If you have a git repo by using git clone  which means you have bare repo and git workspace  you can use git remote add new origin new origin url  and then git push new origin  refs remotes origin    refs heads    and then git push new origin --tags  By this way  you will get a extra head branch  which make no sense

User · Answer

I was in a process of switching from one version control service to another and needed to clone all repositories including all branches  tags and history   To achieve above I did next    manually checkout all branches to local repository  script to checkout all shown below   git push origin          sh script used to checkout all branches to local repository   for branch in  git branch -a   grep remotes   grep -v HEAD   grep -v master    do    git branch --track   branch remotes origin    branch done

User · Answer

I found that none of these seemed to work properly for me  Feel free to flame this to death but for some reason couldn t get the other options to work properly   Expected result was a repo  cloned  to another remote  ie from Github to another provider     All branches are created on new remote All branch history are created on new remote     this was missed on every solution I tried   All tags are created on new remote Source moves over  a given  Non-destructive  giving pause to the --mirror option    The major issue I was seeing was either all remote branches didn t get recreated in the new remote  If a command did  the new remote did not have the branch history  ie doing a git checkout branch  git log wouldn t show the expected branch commits    I noticed git checkout -b branchname is NOT the same as git checkout branchname  the latter being what I needed   I notice git checkout --track branchname didn t appear to pull the branch history   My Solution  powershell based     Function Git-FetchRemoteBranches    originalbranch    git symbolic-ref HEAD  split      -1   Foreach   entry in  git branch -r      If   entry -like   - gt          branch    entry split  - gt    2  split      1      else   branch    entry split      1    Write-Host  --Trying git checkout   -NoNewline Write-Host   branch  -Foreground Yellow  git checkout  branch  Remove-Variable branch -Force        Switch back to original branch  if needed If     git symbolic-ref HEAD  split      -1   -ne  originalbranch     Switching back to original branch  git checkout  originalbranch Remove-Variable originalbranch -Force      git clone http   remoterepo cd remoterepo Git-FetchRemoteBranches git remote add newremote git push newremote --all git push newremote --tags  Not sure if neeeded  but added for good measure

User · Answer

To push all your branches  use either  replace REMOTE with the name of the remote  for example  origin     git push REMOTE       git push REMOTE --all   To push all your tags   git push REMOTE --tags   Finally  I think you can do this all in one command with   git push REMOTE --mirror   However  in addition --mirror  will also push your remotes  so this might not be exactly what you want

User · Answer

Here is another take on the same thing which worked better for the situation I was in  It solves the problem where you have more than one remote  would like to clone all branches in remote source to remote destination but without having to check them all out beforehand    The problem I had with Daniel s solution was that it would refuse to checkout a tracking branch from the source remote if I had previously checked it out already  ie  it would not update my local branch before the push   git push destination  refs remotes source   refs heads        Note    If you are not using direct CLI  you must escape the asterisks       git push destination  refs remotes source    refs heads             mattalxndr      this will push all branches in remote source to a head branch in destination  possibly doing a non-fast-forward push  You still have to push tags separately

User · Answer

My favorite  and simplest  way git clone --mirror  OLD GIT URL cd  NEW CREATED FOLDER git remote add NEW-REMOTE NEW GIT URL git push  NEW-REMOTE --mirror

User · Answer

Based in  Daniel answer I did   for remote in   git branch   grep -v master   do      git push -u origin  remote done

User · Answer

In the case like me that you aquired a repo and are now switching the remote origin to a different repo  a new empty one      So you have your repo and all the branches inside  but you still need to checkout those branches for the git push --all command to actually push those too   You should do this before you push   for remote in  git branch -r   grep -v master    do git checkout --track  remote   done   Followed by  git push --all

[git] Push local Git repo to new remote including all branches and tags

Examples related to git