Microsoft/vscode

SCM - vscode doesn't remember collapsed state of `staged changes`

Open

#270,454 opened on Oct 8, 2025

View on GitHub
 (7 comments) (1 reaction) (1 assignee)TypeScript (10,221 forks)batch import
bughelp wantedscm

Repository metrics

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

Description

Latest insiders Version: 1.105.0-insider Commit: 03c265b1adee71ac88f833e065f7bb956b60550a

  • Assume you have Staged changes, and now you collapse that section in the scm view
  • Ensure one of the staged file is open in the editor
  • Go to a different view, e.g. file explorer
  • Come back, and the Staged changes is expanded again

Contributor guide

Research direction
Reproduce the bug and inspect how the SCM view stores collapse state. Look at the SCM tree view implementation, specifically the part that persists expanded/collapsed state. Check if the state is being saved correctly when navigating away and restored on return. Consider using VSCode's memento API for persisting view state.
Tech stack
typescript
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
TypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70