DIff false positive

[Jorel Anthor]

I'm having some issue with a false positive diff showing in bitbucket after making a PR;

Situation : 

I added a new file to our codebase that didnt exist before. I copy pasted this file in various folder, where the file was missing as well.

Expectation : 
The whole file should be considered new, and highlighted properly to inidicate that every line, is new to the codebase.
No change delta should exist.

Reality:
The whole file isn't marked as new.
There seems to be stuff that have been deleted, which is nonsensical in the scope of a new file.

Is there something that i am missing ? We're having similar shenanigans with bitbucket recently, that should probably be its own post so i wont discuss it further 

[Derick Downey]

My two thoughts are: Is it possible your history got changed/corrupted somehow? Did someone else rebase a branch and then you committed to an older local copy of the branch without rebasing first? We've had nightmare before where someone did this and it caused Bitbucket in the "diff" view to compare two totally separate files with each other, it was weird. My other thought is that it could be the result of them using "two-way diffs" instead of "three-way diffs": https://support.atlassian.com/bitbucket-data-center/kb/comparison-of-a-pull-request-diff-between-bitbucket-server-and-data-center-versions-up-to-6x-and-from-7x-onwards/