[Feature] Local Workspace settings

I would like to be able to configure settings that are specific to my user and to a particular workspace. So, ‘local’ workspace settings?

So there would be three locations for settings (for a single-folder workspace):

• user settings
• ${workspaceRoot}/.vscode/settings.json
• ${workspaceRoot}/.vscode/settings.local.json

This way, I can add .vscode/settings.json to git, and share project settings such as “exclude node_modules” but I can gitignore .vscode/settings.local.json and add things specific to that project that I don’t want to share, such as git autofetch.

I originally thought to suggest .vscode/settings.user.json, similar to how VS Pro handles similar configuration, but that might be confusing.

[firelizzard18]

Using a multi-root workspace, even with only one open root/folder, adds a layer of unnecessary complexity. I’m looking for an additional config file that works with a single-root workspace, so I can have the main workspace config file checked in to source control and the additional workspace config file ignored.

[abique]

My initial proposal was very simple: read settings.*.json in addition to settings.json, from ${workspaceRoot}/.vscode. I did not and do not expect VSCode to look in and subdirectories for settings files. This entirely circumvents the issue of scanning subdirectories.

My opinions about .gitignore changes have been expressed thoroughly by others, but I will point out that adding a single entry for /.vscode/settings.*.json is not at all onerous.

This proposal is simple and very good. Why isn’t it done already? It is taking years to do such a simple thing, this is plain bullshit.