Ignoring the .vscode/ directory is good default behavior,
but it's probably best to track the files that define build tasks, debug
configs, documentation, and any system view description files.
The VS Code team is on the record as committing these files as well.
We in the VS Code team share debug and task specific settings as well because we want our team to have the same set of debug targets and task targets for VS Code.
Ignoring the .vscode/ directory is good default behavior, but it's probably best to track the files that define build tasks, debug configs, documentation, and any system view description files.
The gitignore.io sample takes the same approach. https://www.gitignore.io/api/visualstudiocode
The VS Code team is on the record as committing these files as well.
https://stackoverflow.com/a/32979933/3198973
Even people who vehemently argue that .vscode shouldn't be tracked, agree that complex debug configs should be tracked and shared.
https://stackoverflow.com/a/47668283/3198973