Remove vscode settings from repo - #160
Merged
pchickey merged 1 commit intoSep 16, 2026
Merged
Conversation
pchickey
approved these changes
Sep 16, 2026
pchickey
left a comment
pchickey
left a comment
Contributor
There was a problem hiding this comment.
Didn't ever notice that but yes, we want that gone for the reasons cited but also because cargo component is very much not the thing
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
I think developers might want different
vscodesettings depending on which target or part of the project they're working on. So this change just takes the settings out of the repo and adds them to.gitignoreinstead.