Microsoft/vscode

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

Open

#270454 opened on Oct 8, 2025

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

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

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.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
TypeScriptVS Code extension APIUI state persistence
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
The issue is about the SCM view in VS Code not persisting collapsed state of 'Staged Changes'. Investigate how VS Code stores UI state, likely in the workbench storage. Look for related code in src/vs/workbench/contrib/scm/ or state management utilities. The assignee may already have a fix; check comments and linked PRs for clues.