SCM Graph - add Open File action

[satorg]

Type: Bug

There's the "Graph" of commits panel in the "Source Control" tab. It allows to click a commit and see all the changes made in that commit. When I click "Open file" button for a specific file, it opens the version from the commit in a "read-only" mode.

However, there's no way to switch to the current version of that file (if it still exists). I have to use "Go to file" prompt to manually type the file name, find it and switch to it eventually. It is an all-manual routine, which is very slow and annoying.

VS Code version: Code 1.100.3 (258e40f, 2025-06-02T13:30:54.273Z)
OS version: Darwin arm64 24.5.0

[heoh]

Hello, @lszomoru.
I've experienced the same issue, and I'd like to work on this issue as my first contribution.

Before proceeding, I'd like to ask for some advice on a few design decisions to ensure that my approach aligns with the project's standards.

Open Commit File (Read-only) vs Open File (Writable)

I believe both the existing "Open Commit File" functionality and the new feature proposed in the issue are useful.
Therefore, instead of replacing the existing functionality, I plan to add the latter as a new feature.

Since these two similar features will coexist, I've been considering the following two aspects:

Command Icon

For consistency with other VSCode commands, I think the icon for "Open File" should be go-to-file.
For "Open Commit File," I'm considering using the open-preview or git-pull-request-go-to-changes icon.

Action ID Naming

From what I've seen, the existing feature uses the action ID workbench.scm.action.graph.openFile.
However, based on other VSCode Git commands, I believe the following might be more appropriate:

• workbench.scm.action.graph.openFile: Open File
• workbench.scm.action.graph.openCommitFile: Open File at Commit (Read-only)

I'd really appreciate any advice on these points or any other considerations I should keep in mind while working on this.

Thank you.

[heoh]

It seems like this issue has already been resolved in the latest main branch.

[lszomoru]

It seems like this issue has already been resolved in the latest main branch.

Could you please elaborate on this?

[heoh]

This issue can be reproduced in 1.100.3 version, but not in current main.
I'm not sure, but it seems to have been resolved in #249021.

[lszomoru]

#249021 was merged on May15th and the change should be in 1.103.0.

[heoh]

I just tested it myself to make sure.
It was resolved in commit 5e964f6, and it didn't work in commit 49fd851 right before that.

# Count commits
$ git rev-list --count 1.100.3
133039
$ git rev-list --count 5e964f6
133440

[heoh]

This issue can be reproduced in 1.10.3 version, but not in current main.

Sorry, there was a version typo in my comment earlier. 😅
1.10.3 -> 1.100.3