Right on. Git is good at what it does, but its CLI is too low-level. It feels more like an assembly language than an end-user language, and a haphazard one at that.

There are wrappers that make it much more approachable. IntelliJ’s Git frontend, for example, is pretty nice.

▲ skydhash 8 hours ago | parent [-]

Git is a cli software. If you find yourself repeating a set of commands, what you should do is abstract it using an alias or a script. And you will have you own nice interface.

▲ everybodyknows 4 hours ago | parent | next [-]

My git experience got a lot better after I built scripts and customized the git config files to fully exploit:

  git-log --graph --reflog

  git-commit --amend

  git-cherry-pick

Also, becoming fluent with creation of and switching between local, short-lived branches.

With the above in order, I found I could subset the git state model:

* temporary branches rather than the "stash"

* commit tentative work to HEAD; amend, discard or set aside in a temporary branches rather than as later discoveries require

* side-step the index/cache/staging_area for most operations -- transfer directly between work tree and HEAD commit

▲ esafak 6 hours ago | parent | prev [-]

That's a cop out. Not every CLI sucks so bad it needs a wrapper.

▲

eigencoder an hour ago | parent [-]

No it's not -- powerful CLIs with lots of features are made to be wrapped

	▲	janalsncm 14 minutes ago \| parent [-]
		Even as a CLI it’s not great. git checkout is extremely overloaded.