4 ms·

I always wonder how using cli to commit changes is faster than using dedicated git frontends such as Fork to do such tasks. I used to use it like that but it w

I always wonder how using cli to commit changes is faster than using dedicated git frontends such as Fork to do such tasks. I used to use it like that but it was too much work to manage multiple repositories in such way especially if i didn't remember all changes I made. Using Fork greatly reduced time spent making useful commit messages by having all changes visible at glance. It even allows to stage specific lines of source code and has insanely good interactive rebase UX. Things like that are impossible to achieve with only using cli productively. Also I like the ability to see commits from all branches at glance.

abluecloud 6y ago
I used to think the same, then I learned a bit more about how to use git on the cli. I'm not saying you haven't, I'm just saying for me, I was able to perform tasks quicker with a few tweaks. Things i've done to do this - replace default diff tool (I use https://github.com/so-fancy/diff-so-fancy https://github.com/so-fancy/diff-so-fancy) - added many alias for commonly used commands and ones I often forget - use `git add -p` (or `g a -p` in my setup) which goes through changes file by file, allowing me to add bits i want (this was the main thing I loved about a GUI based git client)