每次我谷歌如何做到这一点，我最终都会读到同样的帖子，但它并没有让我到达我需要的地方，所以希望这对我未来的自己和其他人也有帮助。

我开始了一个新的本地项目，我想把它推到我的回购(比特桶)。以下是我所做的:

导航到本地项目根目录 初始化:git init 使用:git Add添加所有文件。 git commit -m“初始提交” 去我的回购(BitBucket) 创建新的存储库:new_project 回到我的本地项目 add origin git@bitbucket.org:AndrewFox/new_project.git 使用:git Push origin master -f来提交

-f标志用于强制执行，否则它将识别出两个回购是不同的并失败。

我找到了最好最简单的方法https://www.metaltoad.com/blog/git-push-all-branches-new-remote，对我来说就像一个魅力，它会把所有的标签和分支从原点推到新的遥控器:

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

对我来说，有效的方法是。

git push origin --all

以下是我解决[远程拒绝]时，我将本地Git回购到新的远程，包括所有分支和标签

Git克隆——镜像old-repo cd < name-repo.git > Git远程添加新的new-repo Git push new——mirror

我正处于从一个版本控制服务切换到另一个版本控制服务的过程中，需要克隆所有存储库，包括所有分支、标签和历史记录。

为了实现以上目标，我做了下面的事情:

手动签出所有分支到本地存储库(脚本签出所有如下所示)， Git push origin '*:*'

.sh脚本用于检出所有分支到本地存储库:

for branch in `git branch -a | grep remotes | grep -v HEAD | grep -v master `; do
   git branch --track ${branch#remotes/origin/} $branch
done

这里有另一个对同一件事的看法，它更适合我所处的情况。它解决了您有多个远程的问题，想要克隆远程源中的所有分支到远程目标，但不需要事先检查它们。

(我与丹尼尔的解决方案的问题是，它将拒绝从源远程签出跟踪分支，如果我之前已经签出了它，即，它不会在推送之前更新我的本地分支)

git push destination +refs/remotes/source/*:refs/heads/*

注意: 如果你不直接使用CLI，你必须转义星号: Git push destination +refs/remotes/source/\*:refs/heads/\* @mattalxndr

这将把远程源中的所有分支推到目标中的头分支，可能执行非快进推。你仍然需要分别推送标签。