SCM Working Sets: Creating a new branch restores old working set if identically named branch existed in the past

[SimonHeybrock]

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

• VS Code Version: 1.96.3
• OS Version: Mac & Linux

Steps to Reproduce:

In the settings, set scm.workingSets.enabled to true and sc.workingSets.default to "current". Then

git switch main  # close all editors
git checkout -b abc  # now open a file
git switch main  # VScode closes editors if SCM>Working Sets is enabled
git branch -D abc
# <time passes>
git checkout -b abc  # Unexpected behavior: Restores editor from step 2!

Expected behavior:

I would have expected to restore state only when switching branches, not when creating new branches. It seems VScode erroneously detects git checkout -b as a branch switch instead of a new branch creation if a branch of the same name existed in the past?

[vs-code-engineering]

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.96.4. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

[vs-code-engineering]

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[gjsjohnmurray]

Perhaps the Git: Delete Branch... command should also delete the associated local storage of the branch's working set data. It wouldn't solve the OP's issue though because their branch delete was done at the command line.