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
💡 Is your feature request related to a problem? Please describe.
Yes. I want a better way to see the changes history in time line of my settings,
and the Gist is not a good place to do that.
💡 Describe the solution you'd like
It will be good with we could use a normal public GitHub repository instead of a Gist.
💡 Additional context
GitHub repositories have some useful features to make history checking,
like opening the repository in https://github.dev/ and using online VSCode IDE.
Off course: I could clone the gist in my machine and use a local VS Code to do this. But I use Windows,
and there are some problems in the file names created with this extension when I clone the gist in a Windows machine.
The text was updated successfully, but these errors were encountered:
I made a "manual workflow" that is working so far. This workflow does not provide many features, but it allows me to use a regular repository (not a gist), which I think is better, and also to sync extensions files. If you want use it, I put the steps in this instruction. Hope it helps someone.
💡 Is your feature request related to a problem? Please describe.
Yes. I want a better way to see the changes history in time line of my settings,
and the Gist is not a good place to do that.
💡 Describe the solution you'd like
It will be good with we could use a normal public GitHub repository instead of a Gist.
💡 Additional context
GitHub repositories have some useful features to make history checking,
like opening the repository in https://github.dev/ and using online VSCode IDE.
Off course: I could clone the gist in my machine and use a local VS Code to do this. But I use Windows,
and there are some problems in the file names created with this extension when I clone the gist in a Windows machine.
The text was updated successfully, but these errors were encountered: