- never commit
.vscode/settings.json- with the weird exception ofsearch.exclude. If you really need to, be very careful of putting only settings particular of your project that you want to enforce to other developers. - for validation, formatting, compilation use other files like
package.json,.eslint,tsconfig.json, etc - The only .vscode that makes sense to include are complex launch configs for debugging.
- Be careful, there could be a third party extension in your system that could put private information there !
What you can't do is copy & paste the whole settings.json contents file to .vscode/settings.json. I'm seeing some people doing this and committing the file is an atrocity. In that case you will not only break others workspace but worst, you will be enforcing settings to users that you shouldn't like aesthetics, UI, experience. You probably will break their environments because some are very system dependent. Imagine I have vision problems so my editor.* user settings are personalize and when I open your project the visuals change...
Summary: If you are serious don't commit .vscode/settings.json. In general, settings that could be useful for a particular project like validation, compilation, makes sense but in general you can use particular tools configuration files like .eslint, tsconfig.json, .gitignore, package.json. etc. I guess vscode authors just added the file for simplifying newcomer experience but if you want to be serious don't!