this post was submitted on 15 May 2024
7 points (81.8% liked)
Visual Studio
79 readers
1 users here now
A community for the visual studio IDE. https://visualstudio.microsoft.com/
founded 9 months ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.