4 ms·

Why not the command line? One look at that UI and I cannot fathom why it needs all those buttons. push, pull, checkout, add, commit. I can go days just using t

by nahname 14y ago

Why not the command line? One look at that UI and I cannot fathom why it needs all those buttons. push, pull, checkout, add, commit. I can go days just using those five commands.

andypants 14y ago
It has some useful features that I find easier to use in a gui than using command line. For example, being able to see a summary of diffs of all staged and unstaged files, and being able to select particular lines of the diffs and stage/unstage/undo them. Or being able to see commits and diffs from other peoples' branches before I pull them. Honestly, a gui is pretty useful for git, especially when you're doing operations that you want to apply to many specific files in different folders. > push, pull, checkout, add, commit. I can go days just using those five commands. You're missing out on a few git features then. I agree some of the buttons are useless, like adding or removing files. The main window has a list of staged and unstaged files and I just drag and drop files between the two window panes. I've never had to use those buttons before.
- nahname 14y ago
  >You're missing out on a few git features then. Including diff, which I forgot, what else do you use everyday?
  - robin_reala 14y ago
    Merge, fetch, rebase, and blame are all daily commands for me.
  - andypants 14y ago
    log, branch, merge, mv, rm, status, fetch, reset Some more that aren't used everyday, but certainly quite often
    - nahname 14y ago
      Oh, can't believe I forgot to include status.
sergiotapia 14y ago
You're kidding me right? 'git log' is a POS at really understanding the changesets and what changed when. A GUI is INFINITELY easier to use, especially for larger teams. Just click a changeset, see what files were changed and click them to see a diff. ESSENTIAL. If you're hacking on a solo project with only three files then yes, the command line is more than enough, but as for me, I'm really grateful for a GUI as beautiful as this.

by nahname 14y ago

Why not the command line? One look at that UI and I cannot fathom why it needs all those buttons. push, pull, checkout, add, commit. I can go days just using those five commands.

andypants 14y ago

It has some useful features that I find easier to use in a gui than using command line. For example, being able to see a summary of diffs of all staged and unstaged files, and being able to select particular lines of the diffs and stage/unstage/undo them. Or being able to see commits and diffs from other peoples' branches before I pull them. Honestly, a gui is pretty useful for git, especially when you're doing operations that you want to apply to many specific files in different folders. > push, pull, checkout, add, commit. I can go days just using those five commands. You're missing out on a few git features then. I agree some of the buttons are useless, like adding or removing files. The main window has a list of staged and unstaged files and I just drag and drop files between the two window panes. I've never had to use those buttons before.

nahname 14y ago
>You're missing out on a few git features then. Including diff, which I forgot, what else do you use everyday?
- robin_reala 14y ago
  Merge, fetch, rebase, and blame are all daily commands for me.
- andypants 14y ago
  log, branch, merge, mv, rm, status, fetch, reset Some more that aren't used everyday, but certainly quite often
  - nahname 14y ago
    Oh, can't believe I forgot to include status.

sergiotapia 14y ago

You're kidding me right? 'git log' is a POS at really understanding the changesets and what changed when. A GUI is INFINITELY easier to use, especially for larger teams. Just click a changeset, see what files were changed and click them to see a diff. ESSENTIAL. If you're hacking on a solo project with only three files then yes, the command line is more than enough, but as for me, I'm really grateful for a GUI as beautiful as this.