Microsoft/vscode

SCM Working Set - persist pinned tabs when switching branches

Open

#214,625 opened on Jun 7, 2024

View on GitHub
 (2 comments) (5 reactions) (1 assignee)TypeScript (10,221 forks)batch import
feature-requesthelp wantedscm

Repository metrics

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

Description

I love the new Working Sets feature (#35307) - nice work! In particular I like setting mine to "scm.workingSets.default": "empty" so I have a fresh slate when switching branches, though it'd be nice if there was a way to persist the pinned tabs when switching branches since the files I have there tend to be ones I need to reference across branches.

I see two approaches to this, in order of preference:

  1. Add another setting named something like "scm.workingSets.persistPins": true where pinned tabs are maintained globally across working sets. If you close/open a pinned tab in one working set, it will remain closed/opened when switching working sets.
  2. Add a third scm.workingSets.default option named something like pinned. This would carry forward just the pinned tabs I have in the current working set if the switched branch doesn't have a working set yet. I don't like this one as much because it means working sets won't always have the same set of pinned tabs when I add/remove pins.

Contributor guide

Research direction
Examine the working sets implementation in VS Code's source code to understand how tabs are saved and restored. Then implement a new setting to persist pinned tabs across branch switches, ensuring pinned tabs remain open when switching working sets.
Tech stack
typescript
Domain
desktop
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60