Bitbucket and VS Code plugin do not show the same diff in PRs

[Victor Ripplinger]

It seems Bitbucket Cloud shows the correct diff whereas the Bitbucket VS Code plugin shows the diff from the latest common ancestor.

[Ian Chamberlain]

Just to add to this, I noticed that when my local checkout did not exactly match the PR target branch, I would get some differences between my local branch and the target branch included in the PR diff view. A workaround is to git checkout the PR target branch, then "Refresh Pull Requests" and open the diff again.

I also wonder if #586 is related, but seems to happen in different circumstances.

[Gustavo Jacob]

I have the same issue here..

For me it seems to be related to the original PR was created from a old version of a branch, i. e., the PR was made, someone else has modified the original target branch of the PR.

On the Bitbucket Cloud everything is ok, but on the vs code extension, it is like if it is comparing with the original version of the target branch used for creating the PR instead of the actual state of the target branch of the pr.

I have tried to checkout to the target branch and pull it, but the problem remains..

‌