-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove .vscode from version control #29285
Comments
I'll make a PR for it later if there are no hard objections to this. |
Doesn't VSCode have a "default workspace settings" system exactly for this purpose? |
Not an expert on these particular settings, but stuff like formatter settings definitely should belong in the workspace settings. |
Didn't find such functionality in VSCode. Only thing I found is this ancient issue, which was not worked on yet it seems. You got a link?
It probably should. But that's a bit out of scope for this issue. |
#242) …tings removal from VCS in [#29285](space-wizards/space-station-14#29285).
Description
.vscode settings being in VCS forces everybody to use them and prevents customization. Workspace settings override user settings. Which means you effectively can't customize workspace settings for this project at all without your changes ending up in VCS, which is very likely an undesirable outcome.
I believe the right thing to do here would be:
That way we can still distribute configuration changes/templates if need be with devs retaining the ability to change their local workspace settings including settings.json, tasks.json and launch.json.
The text was updated successfully, but these errors were encountered: