为什么没有“git flow feature pull”？跟踪？ [英] Why doesn't "git flow feature pull" track?

问题描述

可以说我已经用 git flow feature start FEATURENAME

创建了一个新功能，然后将它与 git flow feature publish FEATURENAME

现在我的同事想和我合作这个功能， p>

git flow feature pull FEATURENAME

根据远程回购中的功能分支，在他本地的回购中分支。但是，这并没有设置他的本地功能分支来跟踪远程功能分支，所以现在他必须手动跟踪这个分支。

这是什么原因额外的步骤？为什么不让功能拉动命令集来追踪？

什么是 git flow feature pull 和 git flow feature track 。

在哪些情况下你会使用每一种？

解决方案

听起来就像你正在使用 git flow feature pull ，你应该使用 git flow feature track ，因为它创建一个追踪远端的本地分支。

我真的不知道为什么我会使用 git flow feature pull 。它创建了一个没有跟踪的本地分支，我不知道为什么这会有用！这也是一个不好的名字，因为拉应该涉及合并，这不。

Lets say I've created a new feature with git flow feature start FEATURENAME

then published it with git flow feature publish FEATURENAME

Now my colleague wants to collaborate on this feature with me, so he does

git flow feature pull FEATURENAME

This creates a new branch on his local repo, based on the feature branch in the remote repo. This does not however set his local feature branch to track the remote feature branch, so now he has to track this branch manually.

What is the reasoning behind this extra step? Why not have the feature pull command set to track as well?

What's the workflow difference between git flow feature pull and git flow feature track.

In which cases would you use each of those?

解决方案

Sounds like you are using git flow feature pull, where you should be using git flow feature track, since that does create a local branch that tracks the remote.

I can't really think of why I'd ever use git flow feature pull. It creates a local branch with no tracking set up on it, and I don't know why that would be useful! It's also badly named, since a pull should involve a merge, and this does not.

这篇关于为什么没有“git flow feature pull”？跟踪？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！