Same here, but SourceTree just seems to get so slow after a fair amount of use.
SourceTree crashes like all hell for our team. I like the pretty visualisation of the branches, and it's not bad for git newbies, but it actually feels like a relief using the command line most of the time.
Is there a reason to use SourceTree a lot? I only fire up Source Tree when I'm feeling too lazy to compose a search command from the terminal. Of course, `git log | grep phrase` usually does the trick but if I need anything fancier (date ranges, for instance) I'll just fire up ST.
I use it to read commit log messages and see what changes were made to the files.
For actual commiting, branching, etc I just use the terminal.
I use it mostly for the graphs... We work between a ton of branches and it's nice to see the visualization. Also, it's a lot faster when I have to push multiple branches to multiple repos (looking through 2 remotes with 7 branches each right now).
what does its visualization offer that gitk --all doesn't?
Visually tracking merges. Even minimalist command-line-only people I know use basic GUI apps like gitk for this.
Yeah, the bugs (it occasionally needs a full restart) in SourceTree definitely hold it back. I'm willing to put up with them for all the other features, but I can understand how others wouldn't.
I think the support for squashing that Tower has, is far better (or easier to use) than how interactive rebase works in SourceTree. In fact that is the reason I bought Tower. You can squash on merge. In SourceTree I was not able to squash without craeting aditional commits on the way.