3 ms·
I still don't understand why I'd use the command line for git at least. Using a visual tool like Sourcetree I can easily see my staged/unchanged changes, the ou
by trixie_ 6y ago
I still don't understand why I'd use the command line for git at least. Using a visual tool like Sourcetree I can easily see my staged/unchanged changes, the outstanding commits to pull/push of all my branches at a glance without typing anything.
I can easily fetch/pull/push/merge and switch between branches with a click, which is much faster than typing git commands and branch names. I can back merge/rebase changes basically do anything way faster than someone typing in a ton of text to do the same thing.
Plus I can get the same situational awareness across all my repos by just clicking through some tabs. No directory change commands or any further git commands to see the state of things. I feel like I have a better situation awareness, am much faster, and haven't had to type a git command in a long time. I work on a team of many developers who use the CLI and I still don't understand the appeal.
- maxekman 6y agoWith a good CLI setup good speed can be achieved. For example ZSH with the Git plugin from Oh My Zsh and history based autocompletion with arrow up gives you super speed. I rarely type more than a few characters for all my regular operations, including auto completing all branch names and origins.