Is there any way to list all relevant changed files in the "Folder History" view?

[rgeorgiev583]

Right now, there is no way to view the changes in all files in a specific commit in the File History view after the Open Folder History command is used. When a commit is chosen from the list in that view, only the changes in a single file from it are displayed.

I am considering opening an issue for this.

[eamodio]

Are you seeing something different in the File History view, when using the Open Folder History command?

Each commit should be able to be expanded and each file can be diffed.

Was there something else you were expecting?

[rgeorgiev583]

Are you seeing something different in the File History view, when using the Open Folder History command?

Hmm, as far as I remember, the changes used to appear in that view even though I was using the Open Folder History command...

Each commit should be able to be expanded and each file can be diffed.

The commits are actually not expanding for me (there is no dropdown at all). However, I guess that this could be because of something problematic in my specific setup.
I tried to use this feature in a remote devcontainer environment over SSH, which is quite a complex setup. I'll try to reproduce the issue in a minimal, clean environment first.

Was there something else you were expecting?

I expected things to happen just the way you described them.

[rgeorgiev583]

I just tested this feature again in my local environment (no devcontainer, no SSH), and it works just as you described it: after invoking the Open Folder History command, the commits appear in the Folder History view. There is a dropdown for each commit, and it expands to show the list of changed files in the commit when clicked.
However, when I try to use the feature in my devcontainer setup over SSH, the commits are still shown in the File History view, and they won't get expanded with a list of files when clicked: instead, only the diff of a single file (I couldn't determine which one) gets shown to the right.
I'm almost certain that the problem is somewhere in my environment (most probably, the VSCode server needs to be updated), so I don't think there is any point wasting your time with my issue anymore. I'll try to recreate the setup from scratch and I'll check if there would be any difference.
Last but not least, thank you for the great work developing this extension and making working with Git much more comfortable for me :)

[eamodio]

❤️ Thank you! Please let me know what you find -- I would be really interested to know (and fix) any issues that you might find with the remote containers stuff. I would make sure that the GitLens version inside the container is up to date as well as VS Code. FYI, GitLens 12.0 requires VS Code version 1.64 or later.