[英]Gitflow - master and develop diverged
Implemented git branching model as shown below 实现了git分支模型,如下所示
http://nvie.com/posts/a-successful-git-branching-model/ http://nvie.com/posts/a-successful-git-branching-model/
But my branch develop and master gets diverged after these steps 但是我的分支发展和主人在这些步骤之后变得分歧
Step 1 : merge release into master ( no fast forward) 第1步:合并发布到master(没有快进)
Step 2 : merge release into develop ( no fast forward) 第2步:合并发布到开发(没有快进)
since merge commit from step 1 will not be available for step 2 , develop and master gets diverged. 由于步骤1中的合并提交将不可用于步骤2,因此开发和主控变得分歧。
How to ensure develop and master does not gets diverged. 如何确保发展和掌握不会分歧。 ? ?
The git-flow
model naturally makes develop
and master
diverge. git-flow
模型自然地使develop
和master
分歧。 There is no way to follow that workflow and ensure that one of develop
and master
is always an ancestor of the other. 没有办法遵循该工作流程并确保develop
和master
始终是另一个的祖先。
If you have a look at the commits that are in master
and not in develop
, you should see only merge commits: 如果您查看master
中的提交而不是develop
提交,您应该只看到合并提交:
git log develop..master
It means that, if you use the following git-log
command, the output should be empty: 这意味着,如果使用以下git-log
命令,则输出应为空:
git log --no-merges develop..master
If you are not satisfied by this answer, please edit your question to explain why it maters for you that develop
and master
do not diverge from each other. 如果您对此答案不满意,请编辑您的问题,以解释为什么它适合您, develop
和master
不会相互分歧。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.