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

Question

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:

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

Gary · Answer

Hi Stephen,

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

Cheers,
Gary

Seth · Answer

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