Microsoft/vscode

SCM Working Set - persist pinned tabs when switching branches

Open

#214.625 geöffnet am 7. Juni 2024

Auf GitHub ansehen
 (2 Kommentare) (5 Reaktionen) (1 zugewiesene Person)TypeScript (10.221 Forks)batch import
feature-requesthelp wantedscm

Repository-Metriken

Stars
 (74.848 Stars)
PR-Merge-Metriken
 (Durchschn. Merge 11h 43m) (1.000 gemergte PRs in 30 T)

Beschreibung

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