Gutter markers do not match with my Commit comparrison to the Working Tree using the Diff Editor

[shoulders]

I am just bring up this topic again because I found it very frustrating and I was wondering if it was now fixable

Background

• I am reverting some changes I have done over multiple commits so I cannot just use Git revert so my idea was to use GitLens to compare my working tree at various commits and use the "diff arrow" to copy over the relevant changes.

The Issue

• I made most of the changes successfully but there were red lines in the gutter indicating line deletions but I could not see which lines were deleted on either side preventing me from figuring out whether I needed these lines or no.
• The red lines did not match up with any line in particular because they scrolled at their own rate.

Research

So I have spent hours trying to find out why the lines were not showing. and I found the following

• Highlight Code Lines Modified/Created in the Last Commit #4293
  • What you’re looking for (highlighting lines from a specific commit in the gutter while still keeping normal uncommitted change indicators) isn’t supported right now.
  • The gutter colours come from VS Code’s built-in Git integration, which only compares your working tree against HEAD.
  • GitLens doesn’t hook into that in a way that allows overlaying commit-specific highlights.
• Compare against permanently #747
  • I think I may have been confused. It seems like the gutters are from VS code and not from gitlens? I installed gitlens the moment I installed VS code so that probably contributed to my confusion.
  • I guess ultimately I wanted the gutters to diff against origin/master and if gitlens doesn't control that, I'm sorry and I will close this ticket 😅
  • blocked: vscode
  • I tried the following VSCode options to see if this would help me

{
    "editor.renderWhitespace": "all",
    "diffEditor.ignoreTrimWhitespace": false
    "scm.diffDecorationsIgnoreTrimWhitespace": "false"
}

Findings

• GitLens comparison pane — compares whatever two arbitrary refs you pick (historic commit vs. working tree, in your case)
• Gutter indicators — always compares working tree vs. HEAD/index, via VS Code's built-in git decorations, with no setting to redirect it to your chosen historic commit
• GitLens cannot control the Gutters because VSCode does not expose the approriate settings/api to allow control.

Questions

• Is this now fixable?
• Could the documentation be updated to show this issue?
  • I did look but could not find any.