A community for the visual studio IDE. https://visualstudio.microsoft.com/
I think you’ve had a little mixup! Looks like this community is Visual Studio, which is completely unrelated to Visual Studio Code. We can thank Microsoft for that naming disaster 🫠.
If you’re asking about Visual Studio, then the GitHub proposal link isn’t relevant because it’s for VSCode. And if you’re asking about VSCode, then come ask in !vscode@programming.dev
Oh right sorry. I did check it was the good VScode on lemmy.world, but not the programming.dev one -_-'
does the autostash git option work?
That seems great, but I rather have a choice to also port my changes to the new branch ever time I do switch. Will use it if there's nothing else
You'd probably be better off switching to a more powerful git gui like fork
Honestly the only reason I'm using the GUI for switching branches is that I don't want to clutter my terminal with git commands.
Despite it doesn't help me at all. I don't want a separate app. Even more if it's $60 for a wrapper around the cli. I rather learn the cli so I can use it everywhere. And finally... No Linux port.
The reason I recommend it is because you can't rely on the CLI itself. Git commands can do weirdly counter-intuitive things depending on the version and settings of your git install. A command that works for one person may not work for another. Or worse, appear to work and fail silently. Or even worse, cause a problem that you won't find out about until later (if you can even determine the root cause at all).
That's why I recommended Fork.
Also, it's not $60, it essentially has an unlimited evaluation period (a la sublime text) so you can try it out for free for as long as you want, and pay if you want too (I have).
The linux port is in progress.
EDIT: just a sidenote, if you really want to force youself to go CLI only, you'll want to look into how git behaves differently depending on config. I recommend starting with this talk at NDC to get a good enough git config, then move onto Julia Evans blog as she's currently going on a public journey of untangling how the same commands can do different things in modern git.