We are having a real pain with BB right now with mercurial pull requests in bit bucket. For our workflow we have a master repo in BB and a work in progress clone of the master for each developer, also in BB. Devs checkout a copy of their WIP repo onto their machine to do work. They push/pull between their WIP repo in BB and their local copy. So far so normal...
Master (BB) <-> WIP (BB) <-> Local Copy (local machine)
When a feature is completed it is pushed up to the WIP on BB, then the dev issues a pull request from their WIP on BB to the Master repo on BB. All fine and dandy. Someone reviews it, merges it, all normal.
However, if the dev pushes some other work up to their WIP repo before an outstanding PR is merged into Master, the outstanding PR is automatically updated to include this new change set. It also does this completely silently to the dev doing the push.
This is terrible and is causing us severe problems, we see this as a critical bug. It never used to do this. Is there some way of stopping this behaviour?
Any help appreciated.
B
