Have Mercurial Bookmarks Be Sources For Pull Requests

Bitbucket currently doesn't handle Mercurial bookmarks as sources for pull requests, only Mercurial branches. This look to be an attempt to emulate the widely used PR workflow used with git branches. The problem is that HG branches are NOT the equivalent of git branches, rather bookmarks are, this is clearly stated in https://www.mercurial-scm.org/wiki/Bookmarks(Link URL).

This means our mercurial workflow is borked when using BB, as we rely on bookmarks as opposed to heavy weight branches. This manifests itself as automatic updating of an outstanding pull request to a master repo whenever any bookmark on the same branch is pushed to the source repo. This is not helpful behaviour and continually causes us problems and is near impossible to work around without adding in extra staging repos. And no we aren't going to use mercurial branches, they suck in comparison with bookmarks, we'd go to git first, which we don't want to do.

To get the equivalent workflow for a git repo, pull requests need to be issued against hg bookmarks as well as hg branches. If you did this, you'd be supporting HG at the same level as git.