Git Versus Sourcetree

Permalink
I use version control for all my C5 client projects. I use Sourcetree GUI to interact with my repos. Doing commits, creating branches, merging branches and so fourth. Is there an advantage to using just the GIT Command line interface vs Sourcetree GUI? And it is worth me learning GIT for those benefits?

stewblack23
 
JohntheFish replied on at Permalink Reply
JohntheFish
Git command line only becomes near-essential if you are working with projects (such as the core) that already use git. Otherwise, use what you like.
There are some good Git GUIs about, depending on your development OS. You don't have to use the command line.
mesuva replied on at Permalink Reply
mesuva
I'm the same, I use SourceTree for most git tasks and don't really use the command line.

That being said, there have been a couple of ad-hoc tasks where I've had to use a command to fix something, so I'd be suggesting it's worthwhile to at least have an understanding of _how_ to approach using the command line and git.. but the full set of actions and tasks, maybe not.

Personally I like having the visibility of branches and commits all in a nice interface, the command line is just a bit too non-visual for me in this case.
stewblack23 replied on at Permalink Reply
stewblack23
Agreed. I've used the command line to fix commit issues but beside that I just prefer visually being able to see my repo and branches. Especially when two or more people are working on the same project.