Our team has the following setup:
We enabled Bitbucket's automatic merge feature and configured the branching model:
Our problem is that hotfixes on "master" are only being automatically merged into the "develop" branch, but not into the "release" branch.
The automatic merge into our RC worked when we were still creating "release" branches with a version in the name (e.g. "release/1.2.3"). But we decided to have a stable branch for the RC instead, so we don't have to create a new branch everytime we want to create a new RC.
Is there a workaround to make Bitbucket do the automatic merge of hotfixes into our RC although it can't determine an ordering for a branch named "release"?
We are still running Bitbucket 4.14.1, but (hopefully) it will be upgraded by our infrastructure department sometime soon...
Hi everyone, The Cloud team recently announced 12 new DevOps features that help developers ship better code, faster ! While we’re all excited about the new improvements to Bitbucket ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events