chore: Add .vscode to .gitignore #190
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To prevent .vscode from polluting "git" commands. Eventually it may make sense to commit individual files inside .vscode to provide e.g. recommended settings, extensions etc.
Pull Request Test Coverage Report for Build 12925639123Details
💛 - Coveralls |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on recommendations here: https://stackoverflow.com/questions/32964920/should-i-commit-the-vscode-folder-to-source-control, it makes sense to commit individual files only when the project decides to enforce/recommend settings and extensions.
Until then, it is more handy to take it out of the way so that it isn't listed as an untracked change.