Anyone else prefer working with git visually (i.e. Source Tree) rather than on CLI? I like seeing what's going on easily

Easily is type `git <some command>`, and not make some clicks

I fat finger everything... too many typos, so I'm with you on a gui. I like git extensions for Windows.

Yes but dont let anyone hear that you actually like a gui for a cli tool, lest they brandish the pitchforks.

Depends. Can you use CLI and know what is going on with git?

Cli 🙌🏼

@psion1369 Sure you can. I was explaining a cherry pick to a die hard cli guy the other day...

@psion1369 Yes at any point you can open cli and do whatever. In sourcetree theres a button to do just that.

I love PHPStorm to use Git, makes things way easier

I just read my comment and realized I sounded like a dick. What I meant was are you using the GUI as a means to avoid learning the CLI? I know people don't like the GUI usage for git, but I say that as long as you can navigate the CLI as well, use a GUI.

i use both, most of the time i use cli but use gui when everything got difficult after your friend screwed the repositories.

I like `git mergetool` all the time on those difficult merge conflicts. much easier to see.

I do both actually. For simple things with short commands I do CLI. For things that I don't feel like I completely understand or often forget the command to, I use Tower.

I also use Tower, almost exclusively.
There. I admitted it.

IMO GUIs are superior for wading through large diffs before committing them.

There is a very new multi platform GUI named GitKraken that I have been using lately.

If you are using a gui, it'll still be a help to know the cli. I often work on servers through ssh, so the gui isn't a possibility for me

I like using the CLI for the usual commands (commit, push, cherry-pick) etc, but I do always reference SourceTree or something else visual in order to see what I'm about to wreck when I'm dealing with merge conflicts.

@psion1369 Yeah I'm comfortable with CLI and know most of the git commands. I'll try CLI for the rest of the week and see which I prefer. Can imagine dealing with merge conflicts is a pain in the ass

Github for Windows. Although, none of my projects are hosted on github.com 😂

GUI. Always GUI. A have tons of better stuff to do with the brain real estate I'm using to memorise CLI commands (buttons and icons exist for a reason).

If the CLI makes you feel like a real programmer, go make your backend in assembly with a book by your side. No googling though.

I use gui (gitKraken), but still uses cli in case like ssh to server or resolving conflicts or else.

I use a GUI and get some shit from some people. They don't say anything when I don't fuck up my commits tho.

@BellAppLab I just like using CLI so I don't have to leave the terminal because lazy...

Whatever tools get the job done!

@BlackjackCF I respect being tool-agnostic. What I don't understand is insisting on using vim and complaining about missing semicolons, that kind of thing.

i thought we talked about git right here. hahah.

@BellAppLab I like using Vim. It all boils down to personal preference! I don't understand people who push tooling on others :(

@BlackjackCF Fair enough.