[英]Facing issues merging develop to release branch after feature branch got merged to release directly
The way our repo is set up is feature
branch to develop
to release
branch to generate production build.我们的 repo 设置的方式是从
feature
分支develop
到release
分支以生成生产版本。 ie IE
feature
-> develop
-> release
feature
-> develop
-> release
But over the weekend, team merged some hot fixes directly to release.但在周末,团队直接合并了一些热修复以发布。 Now release is ahead of develop.
现在发布领先于开发。 On trying to bring
develop
in sync with release
facing lots of issues.在尝试使
develop
与release
同步时面临许多问题。
I tried to cherry-pick the hot fixes from release
into develop
- skipped the merge commits though.我试图从
release
到develop
中挑选热修复 - 虽然跳过了合并提交。 But even after merging my cherry-picked PR - I see conflicts when trying to raise PR from develop
to release
但即使在合并了我精心挑选的 PR - 我在尝试将 PR 从
develop
提升到release
时也看到了冲突
What am I missing here?我在这里想念什么? Is there a way to fix this?
有没有办法来解决这个问题? Or should we create a new develop branch instead?
还是我们应该创建一个新的开发分支?
Ideally, you would have an hot-fix
branch that you:理想情况下,您将拥有一个
hot-fix
分支:
release
release
develop
develop
that way, Git has recorded merge commits (instead of regular commits through cherry-pick), and that should avoid conflicts, when you PR from develop
to release
later on.这样,Git 记录了合并提交(而不是通过cherry-pick进行的常规提交),并且当您从
develop
到稍后release
时,这应该避免冲突。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.