Summary
When navigating to the line history of a newly added line (e.g., via "Open Line Changes with Previous Revision"), the diff sometimes shows the left side as "missing" — as if the file didn't exist before the commit — even though only the line is new and the file existed in prior commits.
Impact
Users viewing line-level diffs for newly added lines see an unhelpful comparison against an empty/missing file instead of seeing the file's state at the parent commit (without the new line).
Validation
- Open a file and select a line that was added in a recent commit
- Run "Open Line Changes with Previous Revision"
- Verify the left side shows the file at the parent commit, not "missing"
- Verify that lines in files where the entire file was added in a commit still correctly show "missing"
Risk
Low — only affects the fallback when git log -L returns a single commit for line-range history
Summary
When navigating to the line history of a newly added line (e.g., via "Open Line Changes with Previous Revision"), the diff sometimes shows the left side as "missing" — as if the file didn't exist before the commit — even though only the line is new and the file existed in prior commits.
Impact
Users viewing line-level diffs for newly added lines see an unhelpful comparison against an empty/missing file instead of seeing the file's state at the parent commit (without the new line).
Validation
Risk
Low — only affects the fallback when
git log -Lreturns a single commit for line-range history