Quantcast
Channel: Should I commit the .vscode folder to source control? - Stack Overflow
Browsing all 11 articles
Browse latest View live

Answer by Ahsan for Should I commit the .vscode folder to source control?

Yes, you should. I used to be a big advocate of not pushing IDE configs to git, however, things have changed lately for good reasons. I was reading through the Angular 17 .gitignore and found the...

View Article


Answer by Bravo Stack for Should I commit the .vscode folder to source control?

Okay, this may seem pretty late, but if you're finding it difficult to ignore .vscode/ without including any sub-file, you could just ignore the directory:.vscode/and then manually track the file you...

View Article

Answer by Wendel for Should I commit the .vscode folder to source control?

A simple way to keep your settings without commit it in your project git repository is creating a workspace and add folder into it. When do you create a workspace, you need to save a file...

View Article

Answer by LightCC for Should I commit the .vscode folder to source control?

Commit some files in .vscode folderRecommendation is to generally exclude .vscode folder, but leave select JSON files that allow other developers to receive shared settings. If included, these settings...

View Article

Answer by Bumsik Kim for Should I commit the .vscode folder to source control?

Why not just looking at the practice, other than the arguments around here?One of the biggest project that keeps .vscode I found so far is Mozilla Firefox.It looks like the Firefox team shares their...

View Article


Answer by VonC for Should I commit the .vscode folder to source control?

Same as other answers: no.As an illustration, consider the approach chosen by Git 2.19 (Q3 2018), which adds a script (in contrib/) to help users of VSCode work better with the Git codebase.In other...

View Article

Answer by Tymek for Should I commit the .vscode folder to source control?

Between commit/ignore there is third clever option: commit with .default suffix.For example you can add settings.json to .gitignore, and commit settings.json.default, much like it is common practice...

View Article

Answer by cancerbero for Should I commit the .vscode folder to source control?

never commit .vscode/settings.json - with the weird exception of search.exclude . If you really need to, be very careful of putting only settings particular of your project that you want to enforce to...

View Article


Answer by jialin wang for Should I commit the .vscode folder to source control?

The answer is "NO",because .vscode folder is for this editor and you should't push these personal settings to repo in case of confusing others ,so you can add it to your project's .gitignore file to...

View Article


Answer by Benjamin Pasero for Should I commit the .vscode folder to source...

Commit the .vscode folder if you want to share settings, task configuration and debug configuration with the team. I think generally it makes sense to share settings (e.g. whitespace vs tabs) with the...

View Article

Should I commit the .vscode folder to source control?

Is the .vscode folder meant to be committed to source control? In a fresh project, the folder is empty, except the settings.json file. What kind of things would go into this folder? Is it...

View Article
Browsing all 11 articles
Browse latest View live