this post was submitted on 07 Aug 2025
82 points (98.8% liked)
Programming
22057 readers
174 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Git Extensions.
It's what they used at my job when I started, it does the job, and I've gotten used to it. ๐คทโโ๏ธ
I second this, although I'm mostly alone with git extensions in my workplace.
I migrated to from sourcetree some years ago. At the time we had some big generated API client classes (imagine ~60k lines of code). They needed to be regenerated whenever we made changes and the diff on sourcetree was shitting the bed every time I needed to stage the damn files. It was just way too lagy, so I got fed up and moved.
On my personal machine I prefer lazygit or just plain CLI.
I personally prefer lazygit nowadays, but when it comes to GUI clients on Windows then Git Extensions is definitely a very good pick.
I particularly like that it doesn't hide that it's just executing git commands under the hood and its focus on the history graph. Those two things really helped understand how git actually works and why I'm still recommending it.
Yeah, maybe it's because I learned git from the graph, but I find it really helpful when figuring out why a certain piece of code ended up looking like it does (the ability to see the changes made in every commit and open versions of the files at any point in history without checking out the commit is also very useful).
And yeah, if you need or want the command line it always lets you open a git prompt for you to do whatever you want, which is nice.
Also, again maybe because it's what I've gotten used to, but I find the way it handles merge or rebase conflicts more useable (or rather less unusable) than any other I've tried...