Git diff of a renamed file is shown as a new file

[alexisfrjp]

Description

Any diff of a file that was renamed. Git lens doesn't detect the old name and show as a new file.

GitLens Version

17.0.3

VS Code Version

Version: 1.99.3
Commit: 17baf841131aa23349f217ca7c570c76ee87b957
Date: 2025-04-15T23:18:46.076Z
Electron: 34.3.2
ElectronBuildId: 11161073
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Linux x64 4.18.0-553.50.1.el8_10.x86_64

Git Version

No response

Logs, Screenshots, Screen Captures, etc

No response

[wrlssqi]

maybe related issue. vscode 1.101.2, windows 11, gitlens 17.2.0

i do commit0, then change a filename in commit1, then some other changes such as commit2 , commit3. now i an on commit3, working tree clean.

i select commit0 and use "compare with workingtree to Here" function. in the result pannel, i can see the renamed file item, but when click it to open diff editor, the workingtree file (right side) is empty. it didn't open the renamed file in workingtree.

but if i select commit0 and use "compare to/with HEAD" function, it also shows the renamed file item, and this time, when click it, it can show the right diff editor, which compare the files before and after rename.

so the "compare with workingtree to Here" function is mulfunctioned when comparing renamed file.

[nWacky]

Same issue.

Using Git Tree Compare to view the diff between working tree and main seems to resolve the issue for me

[mitchellcgiese]

+1, this issue has been driving me crazy! I always compare my working tree to origin/master or origin/dev and anytime a file gets renamed the diff is completely broken (even though the gitlens SEARCH & COMPARE panel properly detects it as a renamed file).

Git Tree Compare is awesome and exactly what I was looking for. Thanks @nWacky !!

[eamodio]

Sorry for the delay here -- I believe this will be resolved in tomorrow's (v2025.10.01xx) pre-release edition of GitLens? Can you verify that the fix works for you all? Thank you so much!

You can switch to the pre-release edition of GitLens, by clicking on the "Switch to Pre-Release version of this extension" from the Extensions view.

[mitchellcgiese]

Yes that fixed it, thank you so much!