My work process is this: use atoms ui (its very simple) for 99% of my git needs, and in the 1% I need something else, I use the CLI. I don't want every single git feature fit into ui elements on a single screen. I don't want to use the CLI 100%, because its just simply slower, and takes more effort, for most things.
Atom git gui screenshot: https://i.imgur.com/33EkpTu.png
Git kraken screenshot (for comparison): https://www.gitkraken.com/wp-content/uploads/2022/03/index-thumbnail.png
It shows the git tree and includes a diff mechanism. Used it since 2019 after moving from TortoiseHg.
Demo Gif: https://github.com/mhutchie/vscode-git-graph/raw/master/reso...
Extension Page: https://marketplace.visualstudio.com/items?itemName=mhutchie...
I'm a proficient CLI user, but the IDE's GUI really helps with diffs, partial commits, and is all around very convenient to use.
It's fast and nice to work with. I actually use it in conjunction with the command line (zsh w/ autocomplete so I normally only type the first one or two letters of each recurrent command to get the completion, hit return, done) specifically to pick those portions of each file that I want to go into a given commit. Occasionally I use some more advanced features like file history.
As easy as it gets, no Electron boilerplate, full Windows native executable.
1. browsing/searching/sorting commit histories
2. diffs (what you'd expect from a GUI)
3. super lightweight
Cons are: 1. can't resolve conflicts (but it makes easy commits easier)
2. last release was 2014 (but it's perfectly usable as is)
http://rowanj.github.io/gitx/
Screenshot: https://gitextensions.github.io/images/commitlog205.png
Edit: added screenshot
https://alternativeto.net/category/developer-tools/git-clien...