blocks|key|1666353|text|Otto给出的答案是好的，但是所有创建的分支都将以"origin/“作为名称的开头。如果您只想让最后一部分(在最后一个/之后)作为结果分支名称，请使用以下命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1666354|for+remote+in+`git+branch+-r+%7C+grep+-v+/HEAD`;+do+git+checkout+--track+$remote+;+done|code-block|syntax|javascript|1666355|它还有一个好处，就是不会给你任何关于模糊引用的警告。|1666356|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

The answer given by Otto is good, but all the created branches will have "origin/" as the start of the name. If you just want the last part (after the last /) to be your resulting branch names, use this:

<pre><code>for remote in `git branch -r | grep -v /HEAD`; do git checkout --track $remote ; done
</code></pre>

It also has the benefit of not giving you any warnings about ambiguous refs.

blocks|key|1451310|text|你可以很容易地编写脚本，但我不知道它什么时候会有价值。这些分支很快就会落后，你必须一直更新它们。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1451311|远程分支将自动保持最新状态，因此最简单的方法就是在您真正想要处理的位置创建本地分支。|1451312|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

You could script that easily enough, but I don't know when it'd be valuable. Those branches would pretty quickly fall behind, and you'd have to update them all the time.

The remote branches are automatically going to be kept up to date, so it's easiest just to create the local branch at the point where you actually want to work on it.

blocks|key|1666499|text|for+i+in+`git+branch+-a+%7C+grep+remote`;+do+git+branch+--track+${i#remotes/origin/}+$i;+done|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1666500|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>for i in `git branch -a | grep remote`; do git branch --track ${i#remotes/origin/} $i; done
</code></pre>

blocks|key|1666586|text|如果您想要使用powershell，并且您的遥控器名为origin。然后这就行了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1666587|git+fetch++++
git+branch+-r++%7C+%25{$_+-replace+"++origin/"}+%7C+%25{git+branch+--track+$_+"origin/$_"}|code-block|syntax|javascript|1666588|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

If you want to use powershell and your remote is called origin. Then this works.

<pre><code>git fetch 
git branch -r | %{$_ -replace " origin/"} | %{git branch --track $_ "origin/$_"}
</code></pre>

blocks|key|1451423|text|for+branch+in+`git+branch+-a+%7C+grep+remotes+%7C+grep+-v+HEAD+%7C+grep+-v+master`;+do++git+branch+--track+${branch##*/}+$branch;+done|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1451424|使用此命令，您将不会收到这样的警告:+refname‘such+/dev’不明确|unstyled|1451425|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|J|8|@]|9|@]|A|$]]|$1|G|3|-4|5|F|7|K|8|@]|9|@]|A|$]]]|H|$]]

<pre><code>for branch in `git branch -a | grep remotes | grep -v HEAD | grep -v master`; do git branch --track ${branch##*/} $branch; done
</code></pre>

Use this and you will not have such warning as: refname 'origin/dev' is ambiguous

blocks|key|1451715|text|从git+2.23开始：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1451716|for+branch+in+`git+branch+-r+%7C+grep+origin/`;+do+git+switch+-t+-C+${branch#origin/}+$branch;+git+pull;+done|code-block|syntax|javascript|1451717|git+switch的-C标志创建或重置(如果它已经存在)。|offset|length|style|CODE|1451718|git+switch+documentation|1451719|entityMap|0|LINK|mutability|MUTABLE|url|https://git-scm.com/docs/git-switch^0|0|0|0|A|B|2|0|0|O|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|X|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|Y|8|@$I|Z|J|10|K|L]|$I|11|J|12|K|L]]|9|@]|A|$]]|$1|M|3|N|5|6|7|13|8|@]|9|@$I|14|J|15|1|16]]|A|$]]|$1|O|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

From git 2.23 onwards:

<pre><code>for branch in `git branch -r | grep origin/`; do git switch -t -C ${branch#origin/} $branch; git pull; done
</code></pre>

The <code>-C</code> flag for <code>git switch</code> creates or resets if it already exists.

<a href="https://git-scm.com/docs/git-switch" rel="nofollow noreferrer">git switch documentation</a>

blocks|key|1666806|text|VonC的解决方案可以通过更改sed进一步简化(我缺乏直接对他的帖子进行评论的代表点)：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1666807|for+branch+in+$(git+branch+-r+%7C+sed+'s,[%5E/]*/,,g');+do+git+switch+$branch;+done|code-block|syntax|javascript|1666808|通过替换所有非斜杠直到最后一个斜杠，剩余的分支名称适用于本地使用；重复切换到同一分支不是错误(它可能效率较低，但可能比管道中有一个grep更有效:->)。|1666809|switch命令足够智能，可以根据需要跟踪每个远程分支。|1666810|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

VonC's solution can be simplified even further by changing the sed (I lack the rep points to comment directly on his post):
<pre><code>for branch in $(git branch -r | sed 's,[^/]*/,,g'); do git switch $branch; done
</code></pre>
By replacing everything that isn't a slash up to the final slash, the remaining branch name is suitable for local use; repeatedly switching to the same branch isn't an error (it may be inefficient, but it may be more efficient than having a grep in the pipe :-&gt;).
The switch command is smart enough to track each remote branch as necessary.

blocks|key|1451506|text|for+rembranch+in+`git+remote+update+2>&1+>+/dev/null+;+git+branch+-r%7Cegrep+-wv+"HEAD%7Cmaster"`
do+
++++git+checkout+--track+-b+`echo+$rembranch%7Cawk+-F\/+'{print+$2}'`+$rembranch;+
done|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|1451507|解释：|unstyled|1451508|第1行：'git+branch+-r‘(后跟'git+remote+update’以更新远程更改的信息)列出所有远程分支；'egrep+-vw‘用于敲击结果中具有HEAD和master的条目。|1451509|第3行:跟踪指定的远程分支，同时在本地签出它。一个简单的awk用来避免'origin/‘作为本地分支的后缀。|1451510|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|N|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|P|8|@]|9|@]|A|$]]|$1|K|3|-4|5|F|7|Q|8|@]|9|@]|A|$]]]|L|$]]

<pre><code>for rembranch in `git remote update 2&gt;&amp;1 &gt; /dev/null ; git branch -r|egrep -wv "HEAD|master"`
do 
 git checkout --track -b `echo $rembranch|awk -F\/ '{print $2}'` $rembranch; 
done
</code></pre>

Explanation:

line 1: 'git branch -r' (followed by 'git remote update' to update the info on changes to remote) lists all remote branches; 'egrep -vw' is used to knock entries having HEAD and master in the result.

line 3: Track the named remote branch while checking it out locally. A simple awk is used to avoid 'origin/' being the suffix for local branches.

blocks|key|1666697|text|使用bash，如果您想签出所有分支：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1666698|for+remote+in+`git+branch+-r`;+do+git+checkout+$(echo+$remote+%7C+cut+-d'/'+-f+2);+done|code-block|syntax|javascript|1666699|重要的是要注意，当您执行fetch操作时，您不会自动拥有这些分支的本地可编辑副本。|1666700|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Using bash,
If you want to checkout all branches:

<pre><code>for remote in `git branch -r`; do git checkout $(echo $remote | cut -d'/' -f 2); done
</code></pre>

It’s important to note that when you do a fetch that brings down new remote-tracking branches, you don’t automatically have local, editable copies of them.

Tracking a single remote branch as a local branch is straightforward enough. 

<pre><code>$ git checkout --track -b ${branch_name} origin/${branch_name}
</code></pre>

Pushing all local branches up to the remote, creating new remote branches as needed is also easy.

<pre><code>$ git push --all origin
</code></pre>

I want to do the reverse. If I have X number of remote branches at a single source: 

<pre><code>$ git branch -r 
branch1
branch2
branch3
.
.
.
</code></pre>

Can I create local tracking branches for all those remote branches without needed to manually create each one? Say something like:

<pre><code>$ git checkout --track -b --all origin
</code></pre>

I've googled and RTMs, but have come up bunk thus far.

Track all remote git branches as local branches

将单个远程分支作为本地分支进行跟踪非常简单。$ git checkout --track -b ${branch_name} origin/${branch_name}将所有本地分支推送到远程，根据需要创建新的远程分支也很容易。$ git push --all origin我想做相反的事情。如果我在一个源上有X个远程分支：$ git branch -r branch1branch2branch3.

问将所有远程git分支作为本地分支进行跟踪
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将所有远程git分支作为本地分支进行跟踪EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问将所有远程git分支作为本地分支进行跟踪
EN