Refs: #92467

• anyOS @weinand
• anyOS @Tyriar

Complexity: 2

Dirty workspaces are either single-folder or multi-root workspaces that contain untitled files with changes or normal files with changes that are not saved. We typically restore all workspaces with dirty files because we restore all windows when you exit VSCode and start again. But there are cases where you can let VSCode NOT restore them:

• open some windows
• have dirty files in some or all
• File > Exit
• from the command line open code on a folder (code-insiders <folder>)

However, we still want people to find workspaces with dirty files to restore. As such, the list of recently opened workspaces will always show workspaces with dirty files.

Verification:

• verify that we do NOT restore folders and workspaces with dirty files if you instruct code to open a specific folder as instructed above
• verify that the list of recently opened workspaces always indicates dirty workspaces (with a black dot where the close button is)
• verify that you cannot remove a workspace with dirty files from the picker without reviewing the files first and either saving or reverting them