Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Automatic Branch Merging Git Flow Direction and Number of Merges

I have gone through existing threads but they are either too old or are just related and to not resemble completely the question I'd like to ask.

So I am having trouble understanding what the workflow of automatic merging is. There is only one automatic merge performed, regardless of the number of release branches and conditions (semantic versioning in place, branches ordered). Documentation states that branches matching the name of the pull request target are added into the merge path and that there is a limit of 30 merges.

Example: branches are develop (development), release/1.0, release/2.0, release/3.0

I create a pull request from bugfix branch to release/1.0. After the merge, automatic merge merges solely to release/2.0 branch (not to release/3.0 and not to develop). Further (the same, pull req merged to 2.0 merges additionally only to 3.0). Why is that?

0 answers

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

New improvements to user management in Bitbucket Cloud 👥

Hey Community! We’re willing to wager that quite a few of you not only use Bitbucket, but administer it too. Our team is excited to share that we’ll be releasing improvements throughout this month of...

3,762 views 10 16
Read article

Community Events

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

Events near you