7 ms·
Same here, but SourceTree just seems to get so slow after a fair amount of use.
by brbcoding 12y ago
Same here, but SourceTree just seems to get so slow after a fair amount of use.
- bshimmin 12y agoSourceTree 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.
- notduncansmith 12y agoIs 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.
- sergiotapia 12y agoI 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.
- brbcoding 12y agoI 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).
- lttlrck 12y agowhat does its visualization offer that gitk --all doesn't?
- nailer 12y agoVisually tracking merges. Even minimalist command-line-only people I know use basic GUI apps like gitk for this.
- nailer 12y agoYeah, 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.