blocks|key|709899|text|我能想到的一个例子是，如果你有一个“稳定”分支。如果你能创建一个新的分支，比如“实验”，让它跟踪稳定的分支，那就太好了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|709900|git+checkout+--track+-b+experiment+stable
*+do+some+experiments+with+some+commits+*
git+push|code-block|syntax|javascript|709901|除此之外，这可能是为了一致性(这只是一个猜测)。|709902|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|$]]

One example I can think of is if you have a 'stable' branch. Then it would be nice if you could make a new branch, 'experiment' for example, and let it track the stable branch.

<pre><code>git checkout --track -b experiment stable
* do some experiments with some commits *
git push
</code></pre>

Other than that it might be for consistency (that's just a guess).

blocks|key|709932|text|让一个本地分支跟踪另一个本地分支时，脑海中浮现的主要事情是(1)来自Git的关于分支在被跟踪分支的前面/后面的更多通知消息，以及(2)触发器挂钩。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|709933|Git显示更多信息的一个区域是创建分支时。创建basic+branch如下所示：|offset|length|709934|$+git+co+-b+A+master
Switched+to+a+new+branch+'A'|code-block|syntax|javascript|709935|而创建一个tracking+branch看起来像这样：|709936|$+git+co+--track+-b+B+master
Branch+B+set+up+to+track+local+branch+master.
Switched+to+a+new+branch+'B'|709937|这将在.git/config中添加以下内容|style|CODE|709938|[branch+"B"]
++++remote+=+.
++++merge+=+refs/heads/master|709939|在分支A和B上提交一些更改之后，在分支A上执行git+status+-s+-b将显示##+A，而在分支B上执行该命令将显示##+B...master+[ahead+1,+behind+1]，从而提供有关分支B和master之间关系的一些快速信息。|709940|您可能希望本地分支跟踪另一个本地分支的另一个方面是触发hooks；特别是在git+push期间触发pre-receive、update、post-receive和post-update。例如，您可能有钩子来触发在持续集成服务器上的构建，执行一些许可证头检查，检查空白格式错误，等等。|709941|entityMap|0|LINK|mutability|MUTABLE|url|http://book.git-scm.com/3_basic_branching_and_merging.html|1|http://book.git-scm.com/4_tracking_branches.html|2|http://book.git-scm.com/5_git_hooks.html|3|http://schacon.github.com/git/git-push.html^0|0|N|C|0|0|0|5|F|1|0|0|3|B|0|0|3|1|5|1|J|1|N|G|16|4|1F|1|1P|X|2V|1|2X|6|0|11|8|1D|B|1P|6|1W|C|29|B|R|5|2|11|8|3|0^^$0|@$1|2|3|4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1D|8|@]|9|@$D|1E|E|1F|1|1G]]|A|$]]|$1|F|3|G|5|H|7|1H|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|1I|8|@]|9|@$D|1J|E|1K|1|1L]]|A|$]]|$1|M|3|N|5|H|7|1M|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|1N|8|@$D|1O|E|1P|Q|R]]|9|@]|A|$]]|$1|S|3|T|5|H|7|1Q|8|@]|9|@]|A|$I|J]]|$1|U|3|V|5|6|7|1R|8|@$D|1S|E|1T|Q|R]|$D|1U|E|1V|Q|R]|$D|1W|E|1X|Q|R]|$D|1Y|E|1Z|Q|R]|$D|20|E|21|Q|R]|$D|22|E|23|Q|R]|$D|24|E|25|Q|R]|$D|26|E|27|Q|R]|$D|28|E|29|Q|R]]|9|@]|A|$]]|$1|W|3|X|5|6|7|2A|8|@$D|2B|E|2C|Q|R]|$D|2D|E|2E|Q|R]|$D|2F|E|2G|Q|R]|$D|2H|E|2I|Q|R]|$D|2J|E|2K|Q|R]]|9|@$D|2L|E|2M|1|2N]|$D|2O|E|2P|1|2Q]]|A|$]]|$1|Y|3|-4|5|6|7|2R|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|15]]|16|$5|11|12|13|A|$14|17]]|18|$5|11|12|13|A|$14|19]]|1A|$5|11|12|13|A|$14|1B]]]]

The main things that come to mind for having a local branch track another local branch are (1) more informed messages from Git regarding a branch being ahead/behind of the tracked branch and (2) trigger hooks.

One area Git displays more information is when creating a branch. Creating a <a href="http://book.git-scm.com/3_basic_branching_and_merging.html">basic branch</a> looks like the following:

<pre><code>$ git co -b A master
Switched to a new branch 'A'
</code></pre>

While creating a <a href="http://book.git-scm.com/4_tracking_branches.html">tracking branch</a> looks like:

<pre><code>$ git co --track -b B master
Branch B set up to track local branch master.
Switched to a new branch 'B'
</code></pre>

This would add the following in <code>.git/config</code>:

<pre><code>[branch "B"]
 remote = .
 merge = refs/heads/master
</code></pre>

After committing some changes on branches <code>A</code> and <code>B</code>, executing <code>git status -s -b</code> on branch <code>A</code> displays <code>## A</code> while on branch <code>B</code> it displays <code>## B...master [ahead 1, behind 1]</code>, providing some quick information regarding the relationship between branches <code>B</code> and <code>master</code>.

The other area where you might want a local branch track another local branch is to trigger <a href="http://book.git-scm.com/5_git_hooks.html">hooks</a>; in particular <code>pre-receive</code>, <code>update</code>, <code>post-receive</code> and <code>post-update</code> during a <a href="http://schacon.github.com/git/git-push.html"><code>git push</code></a>. You might have hooks to, for example, trigger a build on a continuous integration server, do some license header checks, check for white space format errors, etc.

blocks|key|494260|text|在很多情况下，跟踪另一个本地分支是有用的。例如，在一些git工作流程中，有一些措施可以保护master不会直接接收推送请求。一个例子是代码审查或持续集成系统，它必须在提交登陆远程分支之前通过。另一个例子是，当一个项目由一组只接受拉请求的提交者管理时(GitHub项目经常这样做)。作为一名开发人员，我可能希望创建一个功能分支，然后提交该分支以供审查(或者向repo提交者提交一个pull请求)。然后，我可能想要继续本地开发，而我的团队成员异步审查我的代码，CI构建完成。为了在我之前提交的基础上继续开发，我可能会创建第二个本地分支来跟踪我的第一个本地分支。这允许我从第一次提交开始构建，即使提交还没有到达上游远程分支。此外，如果有人建议对我的第一个分支进行代码审查更改，或者CI构建失败，我可以更新该分支，然后将这些更改重新设置为下游本地分支。下面是如何设置一个分支来跟踪另一个本地分支。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|494261|给定一个本地特征分支：|494262|$+git+co+-b+branch-1
$+git+branch+-u+origin/master
Switched+to+a+new+branch+'branch-1'
$+git+branch+-vv
*+branch-1++++++++++++++++9f0c361+[origin/master]+Some+commit+message
++master++++++++++++++++++85ede1a+[origin/master]+Some+commit+message|code-block|syntax|javascript|494263|这表明本地跟踪分支master和branch-1都跟踪origin+remote上的master分支。我现在可以创建另一个分支，并将其设置为跟踪本地跟踪分支branch-1。|offset|length|style|CODE|494264|$+git+co+-b+branch-2
Switched+to+a+new+branch+'branch-2'
$+git+branch+-u+branch-1+branch-2
Branch+branch-2+set+up+to+track+local+branch+branch-1+by+rebasing.
$+git+branch+-vv
++branch-1++++++++++++++++85ede1a+[origin/master]+Some+commit+message
*+branch-2++++++++++++++++85ede1a+[branch-1]+Some+commit+message
++master++++++++++++++++++85ede1a+[origin/master]+Some+commit+message|494265|entityMap^0|0|0|0|9|6|G|8|R|6|16|6|26|8|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|V|8|@$K|W|L|X|M|N]|$K|Y|L|Z|M|N]|$K|10|L|11|M|N]|$K|12|L|13|M|N]|$K|14|L|15|M|N]]|9|@]|A|$]]|$1|O|3|P|5|F|7|16|8|@]|9|@]|A|$G|H]]|$1|Q|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|R|$]]

There are many occasions when tracking another local branch is useful. For example, in some git workflows, there something in place protecting master from directly receiving push requests. One example is a code review or continuous integration system, which must pass prior to a commit landing on the remote branch. Another example is when a project is managed by a set of committers that only accept pull requests (GitHub projects often do this). As a developer, I may want to create a feature branch, and then submit that branch for review (or submit a pull request to a repo committer). I then may want to continue local development while my teammates asynchronously review my code and the CI builds complete. To continue development on top of my previous commit, I may create a second local branch that tracks from my first local branch. This allows me to build from my first commit, even though that commit hasn't made its way to the upstream remote branch. Also, if someone suggests code review changes for my first branch, or the CI build fails, I can update that branch, and then rebase those changes into down-stream local branches. Here is how to set up a branch to track another local branch.

Given a local feature branch:

<pre><code>$ git co -b branch-1
$ git branch -u origin/master
Switched to a new branch 'branch-1'
$ git branch -vv
* branch-1 9f0c361 [origin/master] Some commit message
 master 85ede1a [origin/master] Some commit message
</code></pre>

This shows that local tracking branches <code>master</code> and <code>branch-1</code> both track the <code>master</code> branch on the <code>origin</code> remote. I can now create another branch, and set it up to track local tracking branch <code>branch-1</code>.

<pre><code>$ git co -b branch-2
Switched to a new branch 'branch-2'
$ git branch -u branch-1 branch-2
Branch branch-2 set up to track local branch branch-1 by rebasing.
$ git branch -vv
 branch-1 85ede1a [origin/master] Some commit message
* branch-2 85ede1a [branch-1] Some commit message
 master 85ede1a [origin/master] Some commit message
</code></pre>

I heard that in <code>Git</code>, you can let a <code>local branch A</code> track another <code>local branch B</code>. 

Why would someone want to do that?

In Git, local branches can track one another - how is this useful?

服务器

GitHub

我听说在Git中，你可以让一个local branch A跟踪另一个local branch B。为什么会有人想这么做呢？

问在Git中，本地分支可以相互跟踪--这有什么用呢？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Git中，本地分支可以相互跟踪--这有什么用呢？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问在Git中，本地分支可以相互跟踪--这有什么用呢？
EN