Merging a PR causes source to be 1 behind

[Ali_Beydoun]

Hi, 

We just started using Pull Requests in BitBucket Cloud. We have a dev branch and a master branch. As a test, I checked out dev and made a change. I then pushed it to remote dev. Now dev is one ahead of master, as expected. 

Next, I created a PR to merge dev into master, with Merge Commit as the strategy. After merging the PR, dev became one behind master (presumably because of the merge commit). The only way I am able to 'sync' the branches is by merging master back into dev (and only on my local machine, not thru BitBucket). The merge from master to dev did not change the branching graph, but now dev is in sync with master.

This is unexpected and very bothersome. Why does merging dev to master thru the PR make it 1 commit behind, and how can this be avoided?

Thanks.

[jredmond]

That's expected behavior - the "merge commit" strategy creates a new commit when you merge. If it's a problem, then one of the other strategies may be a better fit for you.