Hello, we want to have a merge strategy our way, but we can't get it straight.
In the beginning, there is a master from the master we create a branch stage and from stage branch we create dev
So far, so good.
Then we start developing in the dev and at some moment we want to test on our test environment we want to go to the stage, BUT!! When we create a pull request, the master is offered as a base branch, NOT STAGE!
And what is even crazier when we want to create a pull request from stage to master as a base branch where we should create a pull request is offered dev!!
Please help us to solve this issue.
The default branch used when creating a pull request is determined by the default branch you have on your repository. If you go to your Repository settings > Branching model and from here you can set your default branch and your production branch. By default master will be your default branch, and it sounds like dev is set as your production branch. Have a look at Branch a repository for more information.
Default branch is not set on "Branching model" on Bitbucket Cloud.
It's set on "Repository settings -> Repository details -> Advanced -> Main branch"
(And for anyone on Bitbucket Server rather than Bitbucket Cloud, it's also on "Repository details" but under "Default branch").
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