Show changed files per commit and force push

[Enubia]

Is your feature request related to a problem? Please describe.
Often we force push onto already present commits (due to commit policies), and the bitbucket browser view shows them as new changes (as expected).

Unfortunately, this is not true when reviewing pull requests via the vscode GUI.

Describe the solution you'd like
The same behavior as the browser view has (new commits/force pushes can be viewed separately)

Describe alternatives you've considered
None other than going into the browser again to check new changes.

[bwieger-atlassian-com]

@Enubia Double checking my understanding of the ask:

1. Create a PR with a single commit on
2. what exactly are you doing here?
3. And then from here, I should see a difference in behavior from web to VSCode. Yes?

[Enubia]

Sorry, I forgot to add some example images

This is what it looks like in VSCode:

And this is the bitbucket browser view:

As you can see, they are the same pull request but the browser view shows them differently by listing each commit (even tho they are amended and force pushed) and file diff, while the VSCode view only shows the one commit but with updated files. This makes it hard to track any changes added after the initial commit.

What I'd like to propose is that the VSCode UI would somewhat reflect the Bitbucket Web UI.

I'm also unsure if it makes a difference that we use the BitBucket Server solution (self-hosted).

[Enubia]

@bwieger-atlassian-com attached images with some more explanation, sorry for my wording initially