When creating a pull request from fork1 branch1, to the parent repository's default branch, the "Close branch after the pull request is merged" option is disabled.
If you are pulling a request across branches, you can have the option to close the branch when your request is merged. Whether you have this option depends on whether the repository is Git or Mercurial. Mercurial repositories always have this option. Git repositories have this option if the repo administrator allows it; Otherwise, the option is greyed out.
This is in the Bitbucket documentation on this page: https://confluence.atlassian.com/display/BITBUCKET/Work+with+pull+requests</span<>>
The reason it is grey out is because you prevented bookmark deletion. This seems to be a bug, as the documentation states that "you can also prevent users from deleting branches (Git) or bookmarks (Mercurial)", which might be equating branches with bookmarks, even though the Branch Management page states the following: "These rules only apply to bookmarks. Users can still close a branch; closing a branch does not remove it from history."
I've added an issue about this problem.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
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 ...
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!
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