I use command line 95% of the time for a few reasons:
There will inevitably be a point in every long-term project where I am going to have to ssh into a server and fix something. Most of the time, you will not have the option to install a GUI in that situation. I'd rather not be lost.
In my experience, folks who have only ever used GUIs lack a fundamental understanding of what is actually happening. I'm sure there are exceptions. I work on a team, understanding git at a less abstract level makes it easier for me to communicate and coordinate with co-workers.
It's fun once you know what's up.
Once you are comfortable with the CLI, GUIs just feel slow. Selecting a branch from a <select> menu? No thanks!
That said, I do use SourceTree when I do not commit soon enough and find myself in a situation where committing everything would be naughty. I find that the one thing git GUIs do well is present diffs in amore comprehensible way.
I'm just going to address the CLI/GUI question.
I use command line 95% of the time for a few reasons:
<select>menu? No thanks!That said, I do use SourceTree when I do not commit soon enough and find myself in a situation where committing everything would be naughty. I find that the one thing git GUIs do well is present diffs in amore comprehensible way.