3 ms·
> You can use the GUI as a complement. No need to commit 100% to command line or 100% to GUI. This. Personally I handle most of Git's CRUD operations through t
by rumanator 7y ago
> You can use the GUI as a complement. No need to commit 100% to command line or 100% to GUI.
This. Personally I handle most of Git's CRUD operations through the command line, but to analyse logs and branches and navigate through the depository's history, I find gitk to be an invaluable tool, albeit ugly as sin.
- bluehatbrit 7y agoAnother "+1" for this approach. I usually default to the CLI for almost everything, however some repositories which have a really messy history I prefer to view the history in a GUI for to speed things up a bit. I'll also sometimes use a GUI if I want to commit hunks of large files as moving through the files and seeing the full context is often a bit easier. I still always prefer the CLI and will use that first, but I'd feel silly dying on that hill for every situation.