DEV Community

Discussion on: Nice looking Git log

Collapse
 
garetmckinley profile image
Garet McKinley

I personally prefer CLI for things like git. I've had too many bad experiences in the past with gui tools. I feel safer knowing exactly what commands I'm issuing

Collapse
 
amaltapalov profile image
Amal Tapalov • Edited

Agree with you. I had such cases too, for ex. Sourcetree sometimes didn't want to launch at all. It sucks.

Thread Thread
 
cadams profile image
Chad Adams • Edited

Sourcetree is terrible don't use that. If you’re on Windows or Mac give Git Fork a try. I used Sourcetree before I loved how it looked and how simple it was but it was slow and buggy it actually made me switch to command line. I just don’t like typing out the commands all the time.

Thread Thread
 
amaltapalov profile image
Amal Tapalov

100% true about Sourcetree.

Thread Thread
 
mirolago profile image
mirolago

I love Sourcetree. It got better. For cherry picking very handy.

Thread Thread
 
jeklah profile image
Jeklah

Use cherry-picking with interactive flag.

Collapse
 
cadams profile image
Chad Adams • Edited

There's a button on Git Fork that shows you what commands it's calling underneath.
image

Thread Thread
 
jeklah profile image
Jeklah • Edited

One of the reasons people prefer CLI over GUIs is the lack of difference between them. A cli is the same wherever, GUIs vary widely from usability to launching. Some have good features some have bad.

Also useful to know if you have to go on site and they don't have a GUI.

Skip to do what you want with CLI with a bit of practice. Git isn't too bad to learn on the CLI anyway.

Thread Thread
 
cadams profile image
Chad Adams

I know CLI and I use it when the GUI doesn’t work. I just find typing the commands every time very tedious. I’d rather click to do what I want.