Skip to content
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

Official support for tracking VS Code configurations, to replicate config on different machines. #88811

Closed
trusktr opened this issue Jan 16, 2020 · 2 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) settings-sync

Comments

@trusktr
Copy link

trusktr commented Jan 16, 2020

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).

@sandy081
Copy link
Member

/duplicate

#2743

@vscodebot vscodebot bot added the *duplicate Issue identified as a duplicate of another issue(s) label Jan 17, 2020
@vscodebot
Copy link

vscodebot bot commented Jan 17, 2020

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.

Happy Coding!

@vscodebot vscodebot bot closed this as completed Jan 17, 2020
@vscodebot vscodebot bot locked and limited conversation to collaborators Mar 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) settings-sync
Projects
None yet
Development

No branches or pull requests

2 participants