I would find this incredibly annoying in the context of a code review if it was the <i>only</i> diff view available.<p>When performing a code review, I like to understand what changed on the branch from merge base. The &quot;tripe dot&quot; diff is perfect for this because I don&#x27;t want to have to think about the new commits on master. That would make the pull request diff appear different on every commit to master. This would be like a constantly shifting kaleidoscope and would make it difficult to maintain a fixed frame of reference during the review.<p>When assessing whether the code is good to merge, I also like to know how much work there is left to do to integrate the changes back to master. And Bitbucket&#x27;s &quot;phantom merge&quot; is certainly useful in this regard.<p>But most of the time as a reviewer I want to see the &quot;triple dot&quot; view on the pull request.