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
At the moment, there doesn't seem to be any official effort by the VS Code team to make VS Code configuration trackable for replicating VS Code configuration on different machines (f.e. installing a new OS, getting up and running with the same settings, extensions, etc).
There are community efforts, for example the Settings Sync extension, but unless I missed it, there isn't anything official from the VS Code team. Not even .gitignore files to tell people what not to track in ~/.vscode or ~/.config/Code/User.
(Sidenote, Atom ships with .gitignore files in the config folders, so tracking the config is easy, and people are more confident they won't track anything they don't need to).
So this is a feature request for the VS Code team to make tracking of VS Code configuration an official feature of VS Code (even if that means simply placing .gitignore files inside the config folders).
The text was updated successfully, but these errors were encountered:
Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.
At the moment, there doesn't seem to be any official effort by the VS Code team to make VS Code configuration trackable for replicating VS Code configuration on different machines (f.e. installing a new OS, getting up and running with the same settings, extensions, etc).
Here's a question on Stack Overflow. https://stackoverflow.com/questions/59779317
There are community efforts, for example the Settings Sync extension, but unless I missed it, there isn't anything official from the VS Code team. Not even
.gitignore
files to tell people what not to track in~/.vscode
or~/.config/Code/User
.(Sidenote, Atom ships with
.gitignore
files in the config folders, so tracking the config is easy, and people are more confident they won't track anything they don't need to).So this is a feature request for the VS Code team to make tracking of VS Code configuration an official feature of VS Code (even if that means simply placing
.gitignore
files inside the config folders).The text was updated successfully, but these errors were encountered: