Wondering how many people use git cmd and how many use different git clients.

I regularly use git cmd. I made a transition from clients a while back because I wanted to learn more about how it actually works and it works just fine for me, except when I have to google something I don't remember (like how to revert local commit)

Git clients will for sure do abstraction which can be both good and bad, but I'm wondering if there are any definitive pros for clients.

Of course I also use the git cmd client. But for simple things like commit and viewing history I also like TortoiseGit.
For me it works fine.

@Ubergeek Indeed, cmd isn't necessarily the best for information presentation.

always, except for dealing with merge conflicts.

@C0D4 Maybe if you get a big pull, but I will usually vim the conflicts

I usually use
git cmd + gitk + git gui

git cli.
Nothing but the best for my projects.

I prefer the cli as well, it feels easy and I can quickly understand what branch I am on. My IDE's git intergration is OK but I don't like it as much since it seems slow compared to the terminal.

I also find the cli easier to check for my git hooks. I do use my IDE for merge conflicts tho.

I've gotten used to the CLI by now. It was simply infeasible to load some of the Git repos I came across into a gui, because they were so large, the GUI would crash or become unusable.

Mind you, I've customised my workflow to use git aliases instead of memorising commands. That makes things so much easier.

Git Bash + Hyper

I use Github client for 95% of the mundane work.

Big pros against CLI are it's super easy to commit only specific chunks or lines, and it's streamlined, so you just click a button to fetch/pull/push. Also, commit visualisation is nice.

Then, the 5% Github doesn't handle is done via CLI. This includes pushing to another remote or on a different branch, stashing, rebasing, or any tricky operation I have to Google.

If you are using only CLI or only a Client, sorry but you are probably limiting yourself or not as efficient as you could be.

Git cli is the best for everything, except speed.
When you want to see what changes are in multiple files, when you want to cherry pick, etc a gui is easier and faster, but not at all necessary.

I have been using gitkraken for a while now, and recently the atom git plugin for when I am lazy, but I generally use the cli

I always use git on the terminal, as I learnt it that way. For merge conflicts I do use meld though (for the sake of selecting the proper diffs)