Bitbucket Closes a Branch Even Though the Merge Failed Due to Conflicts

I just lost two issue branches on bitbucket because I was trying to merge them. I checked the 'close after merging' checkbox intending to close them after they were merged. Unfortunately the merge failed and they were 'closed' anyway.

 

Steps to reproduce:

  1. Create a branch with a commit that conflicts with master.
  2. Attempt to merge the branch with master via Bitbucket's web UI. (Ensure you select the "Close source branch" checkbox)
  3. The merge will fail and you'll be alerted.
  4. Click the browser's back button and you'll see a 404 message because the branch was closed.

 

2 answers

This sounds to me like a genuine bug, which should be reported at jira.atlassian.com

0 vote
Gary Sackett Atlassian Team Oct 07, 2015

Hi Stephen,

Yes - this is a bug reported at https://bitbucket.org/site/master/issues/10242/unintentional-branch-deletions-from-merge.

Cheers,
Gary 

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Piotr Plewa
Published Dec 27, 2017 in Bitbucket

Recipe: Deploying AWS Lambda functions with Bitbucket Pipelines

Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda&nbsp...

1,768 views 1 5
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you