4 ms·

Off topic: but is there anything for life-long git CLI user to gain from by going GUI?

latencyloser 8y ago
As someone who made the opposite transition: no. My colleagues that are still GUI bound are generally slower at accomplishing most day to day tasks. Committing, rebasing, merging, pushing tags, etc.
- rimliu 8y ago
  I wonder, how is that even possible. Like committing you have the same or less amount of work to do. Merging is just drag-and-drop. Rebasing is two clicks.
  - takeda 8y ago
    You really underestimate how fast CLI is.
sempron64 8y ago
I've found graph views and cherry picking to be better experiences in various guis, but generally for graphs I use tig or gitk and for cherry pick I suffer and copy paste commit hashes. The weight of the various guis and the obscurity of internals is usually enough to stop me from using it.
ThrowawayR2 8y ago
If you're comfortable where you are, then no. Personally, I use a mixture of both. For browsing through commit history or viewing diffs before committing / pushing, I find the GUI to be much more convenient. For most other things, I use the command line.
deleted 8y ago
[deleted]
SenHeng 8y ago
- easier to pick partial commits - easy visualisation of where branches split and merge - same easy visualisation of stashes I use both the CLI and GUI. They both have their merits and demerits. While a CLI may have faster commands, a GUI helps a lot when trying to make sense of relationships between commits branches and visualisation in general.
kh_hk 8y ago
The only use I have found for a GUI is partial commits, and for that I use gitk which is already distributed with git.
ThorinJacobs 8y ago
The main benefit for me is the ability to quickly and conveniently see the commit history and diff as well as branches' current position. If you're already comfortable with doing the same in CLI, then you're probably not going to gain a ton. I like Sourcetree for this particularly because its buttons map fairly well to the actual CLI commands that it will be executing, and makes it painless to open a CLI terminal for instances where I want more fine-tuned control.
forgottenpass 8y ago
For me the value is in diffing, merging and browsing the commit graph. Piecemeal staging can be improved looking at the whole file instead of the window `add -p` shows. But... I'm still primarily a CLI user. I've just configured difftool and mergetool to call up Beyond Compare. git gui and gitk make designers weep, but I've never felt hindered or slowed down in what I want to accomplish with them. I'll try a new GUI tool every now and then, and I haven't found any that make me feel more productive than the CLI augmented by the tools above.

As someone who made the opposite transition: no. My colleagues that are still GUI bound are generally slower at accomplishing most day to day tasks. Committing, rebasing, merging, pushing tags, etc.

rimliu 8y ago
I wonder, how is that even possible. Like committing you have the same or less amount of work to do. Merging is just drag-and-drop. Rebasing is two clicks.
- takeda 8y ago
  You really underestimate how fast CLI is.

sempron64 8y ago

I've found graph views and cherry picking to be better experiences in various guis, but generally for graphs I use tig or gitk and for cherry pick I suffer and copy paste commit hashes. The weight of the various guis and the obscurity of internals is usually enough to stop me from using it.

ThrowawayR2 8y ago

If you're comfortable where you are, then no. Personally, I use a mixture of both. For browsing through commit history or viewing diffs before committing / pushing, I find the GUI to be much more convenient. For most other things, I use the command line.

deleted 8y ago

[deleted]

SenHeng 8y ago

- easier to pick partial commits - easy visualisation of where branches split and merge - same easy visualisation of stashes I use both the CLI and GUI. They both have their merits and demerits. While a CLI may have faster commands, a GUI helps a lot when trying to make sense of relationships between commits branches and visualisation in general.

kh_hk 8y ago

The only use I have found for a GUI is partial commits, and for that I use gitk which is already distributed with git.

ThorinJacobs 8y ago

The main benefit for me is the ability to quickly and conveniently see the commit history and diff as well as branches' current position. If you're already comfortable with doing the same in CLI, then you're probably not going to gain a ton. I like Sourcetree for this particularly because its buttons map fairly well to the actual CLI commands that it will be executing, and makes it painless to open a CLI terminal for instances where I want more fine-tuned control.

forgottenpass 8y ago

For me the value is in diffing, merging and browsing the commit graph. Piecemeal staging can be improved looking at the whole file instead of the window `add -p` shows. But... I'm still primarily a CLI user. I've just configured difftool and mergetool to call up Beyond Compare. git gui and gitk make designers weep, but I've never felt hindered or slowed down in what I want to accomplish with them. I'll try a new GUI tool every now and then, and I haven't found any that make me feel more productive than the CLI augmented by the tools above.