Bitbucket has changed the diff algorithm from a '3-way' diff to a 2-way 'three-dot' diff.

Attached is a question and answer about this from Web Archive dated July 15, 2022:

2022-07-15 Solved - On the pull request diff merged commits are displayed - 2080354.pdf

This change was made in order to improve performance, but it has come at a cost of degrading the quality of diffs. The problem is when the source branch includes a merge commit for a code change already completed at the target branch, yet the diff shows this code as if it is newly added, removed, or changed. For the reviewer, it becomes more difficult to tell what actual changes are. Individual commits can be selected for review, but this still causes difficulty when reviewing large change sets with many merge commits and / or many actual commits for feature / bug change.

This has led to 'diff fatigue' and items that are real commits have started slipping through the code review process.

This may not be the case for all companies, which is why the request is simply to allow companies to choose between the performance enhancement of the 2-way 'three-dot' diff and the clarity of the '3-way diff'.

This is important and it needs to be addressed.