From b741ef37f5c9849c53702fd0ac5e9cc952a2829d Mon Sep 17 00:00:00 2001 From: "Christopher J. McClellan" Date: Wed, 1 Jan 2020 07:43:32 -0500 Subject: [PATCH] Track launch.json, tasks.json, md & svd files 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 > 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. https://stackoverflow.com/a/32979933/3198973 Even people who vehemently argue that .vscode shouldn't be track, agree that complex debug configs should be tracked and shared. > The only .vscode that makes sense to include are complex launch configs for debugging. https://stackoverflow.com/a/47668283/3198973 --- .gitignore | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/.gitignore b/.gitignore index 816a738..cc4a880 100644 --- a/.gitignore +++ b/.gitignore @@ -5,4 +5,8 @@ Cargo.lock target/ # editor files -.vscode/ \ No newline at end of file +.vscode/* +!.vscode/*.md +!.vscode/*.svd +!.vscode/launch.json +!.vscode/tasks.json \ No newline at end of file