My team follows a feature branching workflow where each team member creates a feature branch from master, works on changes locally, then submits a pull request against master. We've noticed that if changes are made to master after the feature branch has been created, then the pull request will include both commits from the feature branch (that only exist there) plus commits that have landed on master since the last time master was pulled.
My primary question: is this the way Bit Bucket is designed to work? If so, that seems strange to us (we would expect the PR to only show commits on the feature branch that aren't in master) so my secondary questions: is there a way to get the behavior I'm describing or is there a change we need to our individual workflows (such as always pulling master before opening the PR) to achieve the desired effect?
Daniel
