Hacker News Reader

Hacker News

Comment by burkaman | Hacker News Reader

Parent Full thread

burkaman

The most viewed question is even more relatable: https://stackoverflow.com/questions/927358/how-to-undo-last-...

You can get the top viewed questions here: http://data.stackexchange.com/stackoverflow/query/53109/ques...

View on HN

My own personal top hit is:

https://stackoverflow.com/questions/2003505/how-do-i-delete-...

Pretty sure I've got the command down by now, but it's embarassing how many times I forgot the exact syntax. It was especially bad before the "--delete" syntax was introduced.

TIL --delete, I still `git push origin :branchname`'d just this morning.

Though at least now github provides easily access buttons.

Gotta be honest, when I use git without tab completion for extended amounts of times I end up with a 'delete' branch eventually.

That link was actually marked visited in my browser. Thank god for SO.

Why such a complicated top answer? There should be one command for this without involving esoteric stuff like HEAD, ~ and ...

hey Linus, undo last 1 git command (as though it had never been entered):

  git undo 1

thanks.

Only works for commits, but it's a very useful alias I've picked up.

    [alias]
        undo = reset HEAD~1 --mixed

How about git uncommit? Undo suggests it might work for other actions like pushing

I'll bet between the reflog and aliases you could do that.

How would you undo "git reflog expire"? How would you undo "git push origin -f"?

> How would you undo "git push origin -f"?

Remote reflog contains this info (if enabled).

Of course not all commands would be reversible, especially not plumbing.

> git reflog expire

Is there a valid reason to do this in the first place?

> git push origin -f

No standard way to undo that. Only do it if you must, and you absolutely do what's going to happen. Always do a "got remote update" immediately before the force-push and double-check that the remote branch points to what you expect.

As a general rule, "--force" is short for "you better be prepared to deal with the consequences".

Well let me put the question back to you: can changes to git provide undo for literally every command?

Wouldn't work with commands like `git reset --hard` or `git checkout --force` though. Those commands delete uncommitted changes permanently.

I'm requesting the exact syntax I just wrote.

EDIT: the replies to this don't get how feature requests work. yes, I could write this basic feature myself. thanks.

You can make a bash script named `git-undo` , put it in your path (I use ~/bin):

    #! /bin/bash
    git reset HEAD~1 && git checkout .

You can assign git aliases that execute shell commands by prefixing with an exclamation mark.

So write a script and assign an alias.

You're missing his point. Defaults matter. A huge majority of users (80%?) never change the defaults, often for good reasons.

A minor usability investment on the part of 1-2 git developers would prevent thousands of hours wasted by newbies and perpetual intermediates (https://blog.codinghorror.com/defending-perpetual-intermedia...).

A feature like undo is never going to be implemented as a core thing because there are too many instances where it's not clear what it should do.

Reply on news.ycombinator.com