Source branch in pull request is closed even though I didn't tick the "close branch" checkbox

[Aleks Sotirovski]

I'm not sure why this is happening all of a sudden, usually there are no issues.

Basically I created a pull request to merge our develop branch into master. I was very specific and careful not to select the checkbox that says "Close this branch after PR is merged" (something along those lines). 

I made sure not to tick this when initially creating the PR, and then again when I clicked the "Merge" button it asks again in the modal, but I left it unticked there as well. 

After the merge is complete my develop branch is no longer in the "Active" branches list, and is now showing up in the "Merged" branches list.

Any ideas why this would be happening? 

Are there any cases where BitBucket would close the source branch in a PR even if I have explicitly told it not to?

[jredmond · Accepted solution]

The "Active" branch list shows open branches that have commits which are not on the main branch. The "Merged" list shows open branches that don't have anything that isn't on master. Neither list shows closed branches.

Your branch is still open if it's in one of those lists. You can still push, pull, or do anything else with that branch, whether you're using Git or Mercurial.

[Aleks Sotirovski]

Gotcha, thanks very much!