Comment by nuancebydefault

The cli is faster if you know by heart but a real disadvantage is that it is hard to "see" what you did or what happened in the past. Good look finding where/whether an old branch got merged and find out if it is part of a release, using cli.

harrall a day ago

Is this really true? When I want to reorder commits, I just drag & drop in a GUI and I’m done. Or if I want to switch branch or manage a complex mix of rebases or cherry picks, it’s just 2 or 3 clicks. In CLI, by the time I’ve typed out the commit hash or locator, it’s already taken longer. And I type 130 words per minute.

Reply View 2 replies

dijksterhuis a day ago

> by the time I’ve typed out the commit hash
i don’t think i’ve typed out a full hash in … years? if i have i’ve used the short 8 character hash.
git rev-parse might be something useful to have a look at, especially when combined with aliases.

Reply View | 1 reply
- harrall a day ago
  
  Nah I’m talking about the short hash.
  But I still have to find the short hash too, and then copy or re-type it… With a UI, I just… click click click done.
  
  Reply View | 0 replies