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

When creating the Pull Request, it may propose to merge into the wrong branch




If you create a branch from a release branch, let's say release/1.1, you would expect that Bitbucket by default proposes to merge into this release branch.

Unfortunately, this is not the case, it can propose to merge into master instead for instance.

It is unexpected and a bit error prone.

Thanks to automatic branch merging (which is activated in our case), it should detect the corresponding ancestor.

Is there a solution for this ?

Thanks in advance,




0 answers

Suggest an answer

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

📣 Calling Bitbucket Data Center customers to participate in research

Hi everyone, Are you Bitbucket DC customer? If so, we'd love to talk to you! Our team wants to dive deep to understand your long-term plans regarding Bitbucket DC and Atlassian Cloud. Do you plan...

168 views 2 4
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