Only CLI command I have needed as a software developer for last 6 years of using GitKraken was `git diff <commit_id_1> <commit_id_2> --stat`, because GitKraken still has no feature with exactly the same result. Even this one is better to call from CLI inside GitKraken because of commit IDs suggestion.
Almost all usual and even advanced features of Git can be executed through the GitKraken UI and user knows way much better what will happen - command line can never provide overview like that (it's not a bug, it's a feature).
And you mentioned vizualizing branches - yes, this is absolutely key feature decisive for effective or ineffective work with repositories. Once I have colaborated with a guy, who told me, he is effective in CLI. One day I told him I have pushed the new feature now and he aked me for a branch name. I couldn't help but laugh. I never had to ask anybody a question like this. I immediately see what did who pushed in any brach (and after next click all the details of commit). So I can go straight to the important questions a programmer should be asking in the 2020s. For example: "Why did you do it this way?"
What do you actually gain by using Git in the command line, and why should it remain a command-line-first tool, except for edge cases (especially in the 2020s)?
The most effective git command ever: gitkraken
I think I tried it a long time ago. Probably great for visualizing branches.
As git is a command-line first tool, you'll get the best from git on the terminal.
Only CLI command I have needed as a software developer for last 6 years of using GitKraken was `git diff <commit_id_1> <commit_id_2> --stat`, because GitKraken still has no feature with exactly the same result. Even this one is better to call from CLI inside GitKraken because of commit IDs suggestion.
Almost all usual and even advanced features of Git can be executed through the GitKraken UI and user knows way much better what will happen - command line can never provide overview like that (it's not a bug, it's a feature).
And you mentioned vizualizing branches - yes, this is absolutely key feature decisive for effective or ineffective work with repositories. Once I have colaborated with a guy, who told me, he is effective in CLI. One day I told him I have pushed the new feature now and he aked me for a branch name. I couldn't help but laugh. I never had to ask anybody a question like this. I immediately see what did who pushed in any brach (and after next click all the details of commit). So I can go straight to the important questions a programmer should be asking in the 2020s. For example: "Why did you do it this way?"
What do you actually gain by using Git in the command line, and why should it remain a command-line-first tool, except for edge cases (especially in the 2020s)?
Playbook