Microsoft/vscode

git diff view not updated after unstaging changes of new file

Open

#264,340 opened on Sep 1, 2025

View on GitHub
 (1 comment) (0 reactions) (1 assignee)TypeScript (10,221 forks)batch import
buggithelp wanted

Repository metrics

Stars
 (74,848 stars)
PR merge metrics
 (Avg merge 11h 43m) (1,000 merged PRs in 30d)

Description

Does this issue occur when all extensions are disabled?: Yes

Version: 1.104.0-insider (user setup) Commit: 86f1b8fd472ae9cb26d24121a2476e40b98a0785 Date: 2025-09-01T07:47:15.390Z Electron: 37.3.1 ElectronBuildId: 12259562 Chromium: 138.0.7204.235 Node.js: 22.18.0 V8: 13.8.258.31-electron.0 OS: Windows_NT x64 10.0.19045 Steps to Reproduce:

  1. Add new file
  2. Stage changes
  3. change the file
  4. open diff view
  5. unstage changes

See also #240719

https://github.com/user-attachments/assets/7b9f9d57-c6ca-4b88-b594-a1e17d9111b2

Contributor guide

Research direction
Examine the source control model in VS Code to understand how unstaging a new file affects the diff view. Check the event handling for file changes and diff document updates.
Tech stack
typescriptjavascriptnodejs
Domain
frontenddeveloper experience
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70