最简单的方法是:

git push --all origin

这将推动标签和分支。

首先将远程git添加到您的loacl with中

git remote add remote_name remote_address

而之后你只需要用下面的命令就可以了

git push --all remote_name

我使用下面的命令将所有分支迁移到新的存储库。

~$ 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 master
~$ git push new-origin --mirror

注意:当从Atlassian Stash克隆一个repo到AWS CodeCommit(空白repo)时，我不得不使用第二个最后(即推主第一个)命令。我不确定原因，但在push (git push new-origin——mirror) default branch指的是master以外的一些其他分支。

添加新的远程回购，最后一步将在您推送时排除HEAD分支

git clone <url_of_old_repo>
cd <name_of_old_repo>
git remote add new-origin <url_of_new_repo>
git ls-remote . | grep 'refs/remotes/origin/' | grep -v 'HEAD' | awk -F 'origin/' '{print $2}' | xargs -i git push -f new-origin  --tags refs/remotes/origin/{}:refs/heads/{}

解决方案没有硬编码的配置来源

在全局gitconfig中使用以下命令

[remote]
    push = +refs/heads/*
    push = +refs/tags/*

这将推送所有分支和所有标签

为什么你不应该硬编码的来源配置?

如果你硬编码:

你最终会在所有的回购中使用origin作为遥控器。你不能添加origin，你需要使用set-url。 如果一个工具用不同的名称创建了一个远程，则push all配置将不应用。然后你将不得不重命名远程，但重命名将不起作用，因为原点已经存在(从点1)记住:)

现代git已经在处理抓取了

美国每年Jakub刚纳ębski的答案:

使用现代git，你总是获取所有分支(作为远程跟踪分支)到refs/remotes/origin/*命名空间

我在这里找到了最好和最简单的方法，就像@kumarahul张贴的那样，对我来说很有魅力，它会把所有的标签和分支从原点推送到新的遥控器:

git remote add newremote new-remote-url

git push newremote --tags refs/remotes/origin/*:refs/heads/*

我使用'git push——all -u newremote'，但它只会将检出的分支推到newremote。

Git: Push All Branches to a New Remote by Keith Dechant , Software Architect Here's a scenario some of you might have encountered with your Git repositories. You have a working copy of a Git repo, say from an old server. But you only have the working copy, and the origin is not accessible. So you can't just fork it. But you want to push the whole repo and all the branch history to your new remote. This is possible if your working copy contains the tracking branches from the old remote (origin/branch1, origin/branch1, etc.). If you do, you have the entire repo and history. However, in my case there were dozens of branches, and some or all of them I had never checked out locally. Pushing them all seemed like a heavy lift. So, how to proceed? I identified two options: Option 1: Checkout every branch and push I could do this, and I could even write a Bash script to help. However, doing this would change my working files with each checkout, and would create a local branch for each of the remote tracking branches. This would be slow with a large repo. Option 2: Push without changing your working copy There is a second alternative, which doesn't require a checkout of each branch, doesn't create extraneous branches in the working copy, and doesn't even modify the files in the working copy. If your old, no-longer-active remote is called "oldremote" and your new remote is called "newremote", you can push just the remote tracking branches with this command: git push newremote refs/remotes/oldremote/*:refs/heads/* In some cases, it's also possible to push just a subset of the branches. If the branch names are namespaced with a slash (e.g., oldremote/features/branch3, oldremote/features/branch4, etc.), you can push only the remote tracking branches with names beginning with "oldremote/features": git push newremote refs/remotes/oldremote/features/*:refs/heads/features/* Whether you push all the branches or just some of them, Git will perform the entire operation without creating any new local branches, and without making changes to your working files. Every tracking branch that matches your pattern will be pushed to the new remote. For more information on the topic, check out this thread on Stack Overflow. Date posted: October 9, 2017