You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think a discussion (and possibly future feature implementation) should happen around the fact that some project-specific settings could be shared across an entire team (i.e., you can git-commit alongside the repo —similar to the .vscode/ folder) VS they're user-specific (i.e., should be git-ignored) because it contains personal choices of an individual.
Hey, @nathansobo, thanks! I just want to make sure that I was able to communicate well enough the reason why opened this separate issue: My main concern here was to underline that not all project-specific settings are equal: some could (should?) be git-ignored, whilst other might be shared across a team. Makes sense?
I think a discussion (and possibly future feature implementation) should happen around the fact that some project-specific settings could be shared across an entire team (i.e., you can git-commit alongside the repo —similar to the
.vscode/
folder) VS they're user-specific (i.e., should be git-ignored) because it contains personal choices of an individual.Wdyt?
Possibly related to #5411 and #5443
The text was updated successfully, but these errors were encountered: