简体   繁体   English

在功能分支直接合并到发布后面临合并开发到发布分支的问题

[英]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分支developrelease分支以生成生产版本。 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.在尝试使developrelease同步时面临许多问题。

I tried to cherry-pick the hot fixes from release into develop - skipped the merge commits though.我试图从releasedevelop中挑选热修复 - 虽然跳过了合并提交。 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分支

  • merge to release合并release
  • and you merge to 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.

相关问题 合并开发以释放分支 - merging develop to release branch 问题将Git Feature分支合并到“Beta”分支(在它已经合并到“Develop”分支之后) - Issue merging Git Feature branch into “Beta” branch (after it has already been merged to “Develop” branch) GIT merge develop into feature branch -- 同一个分支被合并和恢复后 - GIT merge develop into feature branch -- after the same branch was merged and reverted git 分支 - 合并功能分支到发布和开发分支 - git branching - merging feature branch to release and dev branch 发布后 Gitflow 在 master 后面开发分支 - Gitflow develop branch behind master after a release Git 流程:合并到发布分支而不是开发分支的影响(也就是更正合并问题的最简单方法) - Git Flow: Implications of merging to release branch instead of develop (aka easiest way to correct merge issues) 功能分支合并到 Master 后发生变化 - Feature branch got change after merging it to Master 功能发布后重建“下一个”分支 - Rebuilding the “next” branch after a feature release 在Artifactory Release Staging之后合并git development分支以使用Jenkins进行掌握 - Merging git develop branch to master using Jenkins after Artifactory Release Staging 合并到开发分支会导致功能分支被删除 - Merging into develop branch causes feature branch to be deleted
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM