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.
Having .vscode checked into the repo causes tons of headaches for me. I use a switch that isn't named
4.14.1
, so I need to have a different.vscode/settings.json
. I also make extensive use of vscode tasks, so mytasks.json
doesn't match either (in fact, the existingtasks.json
is syntactically invalid). To deal with this, I have a number of weird git settings configured. And even still, I often need to run some special scripts when performing various.I'm sympathetic to the
git clean -Xdf
issue, but I think there's a managable workaround to it. The below command will do the desired thing.This of course could be aliased in a
.bashrc
, or also aliased via git aliases so that they can be invoked by a command likegit my-clean
: