Good modern software always offers an undo option. Where is "git undo"?

It’s the first thing in the article. Git reflog. (BTW you won’t get any disagreement from me about the lack of intuitiveness of the command name. But, in a way, git’s whole reason for existing is to undo, and almost everything you do in git can be undone by design.)

The reflog is very helpful but I don't think it counts as an "undo". Some operations (like git add or git push) won't show up in the reflog.

Even the operations which do show will often require more thought to undo than a hypothetical "git undo" would. I know how to use the reflog but I often go out of my way to avoid it because "git branch tmp HEAD; git $POSSIBLE_MISTAKE; git reset ---hard tmp; git branch -D tmp" requires less effort than deciphering the reflog's output.

Git reflog absolutely counts as the first step of undo for several workflows, but you’re right there are other commands needed for some kinds of undo.

Undoing a push does require a different set of commands, but my point, to the question @amelius asked, is that you can undo both push and add, and whatever other mistake you’re thinking of, difficult or not.

Of course, but Git keeps track of everything you undo, which at the meta level is something you can't easily undo ...

Maybe I misunderstood your question, what were you asking about above?

Ah yes, the classic `rm --undo` saved me so many times. No, command-line interfaces rarely offer undo. The onus is on the user to not do irreversible things when they may need to be reversed.

Git, coincidentally, does have something equivalent to undo history: the reflog.

"rm" was made in the '70s. Git was made in the '00s.

Nothing prevents rm from being made to “put in trash bin” in the year 2022. Your argument seems weak. rm removes. mv moves. If you want mv, use mv.

Nobody said that rm was perfect ;)

  git reset HEAD~1 

Usually works good enough for me. Idk if this is the proposed way to undo stuff