Problem Definition

Bitbuckets review essentially hides the changes made by the merge, merge errors are not visible in the review and can, therefore, lead to unexpected errors after merging the feature branch into master. When looking at the history of a change, it becomes hard to identify all the changes that were part of one feature branch, because the changes are essentially split up into the before-the-merge and after-the-merge part.

Suggested Solution

Provide possibility to create customized tip (as for the merge conflicts) to recommend the developers to switch to certain merge strategy for this single pull request instead of using the default one.