Using a git GUI is like dulling a sharp knife in fear of cutting yourself.

And here my fking git on Windows is throwing ssl error. Ssl is broken, and I am tired of finding a solution. Life is easy with command line on Linux.

@rookiemaverick disable ssl verification 😂

Actually don’t do that 😉

I donno, I find GIT GUIs are much better for visualization and handling rebasing. CLI is good for other tasks, just use the right tool for the job.

Git cli for normal stuff (commit, branching, push, pull, ect)

A GUI is handy for merge conflicts, logs ect.

@aether I love git cola for being able to pick lines I go and don't want to commit. Number of times I've got some code that really has two of three changes in it that can be separated out. Commit lines, compile (maybe quick unit test), commit next set and repeat.

Certain topics have no middle ground.

For example, try proposing a compromise between tabs and spaces and soon a nice contingent from both camps will gather up and burn you as a heretic.

I think git is different. Give tig a try.

I use 95% command line, but I like how Gitkraken has extra GitHub/Gitlab/etc integrations.

For example: When I want to quickly do code reviews, cleanups and merges on a bunch of pull requests while filtering them by CI status, I like it better then using Github's interface.

@karelian Three spaces for the win.

@bittersweet I'll suggest it is language specific although what I really want to say is WTF 3?!

@TafT

Without joking, I really feel 3 is perfect. Two doesn't stand out enough, four is a bit much. I only use it as a default for Haskell projects though.

No, I feel it's more like driving auto instead of manual gear

I use gitkraken a lot, but since a found `git add -i` and `git add -p` i use it less.

I like to see the pretty merges and charts tho.

@TafT yeah partial committing using GUIs is a use-case that just seems more natural via a GUI than CLI interactive mode. I like using VS Code’s keybinds for (un)stage / revert selection.