6 ms·

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

• logicallee 9y ago
  hey Linus, undo last 1 git command (as though it had never been entered): git undo 1 thanks.
  • emodendroket 9y ago
    I'll bet between the reflog and aliases you could do that.
    • kccqzy 9y ago
      How would you undo "git reflog expire"? How would you undo "git push origin -f"?
      • majewsky 9y ago
        > 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".
      • hdhzy 9y ago
        > 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.
      • emodendroket 9y ago
        Well let me put the question back to you: can changes to git provide undo for literally every command?
    • logicallee 9y ago
      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.
      • emodendroket 9y ago
        So write a script and assign an alias.
        • oblio 9y ago
          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-intermediacy/ https://blog.codinghorror.com/defending-perpetual-intermedia...).
          • emodendroket 9y ago
            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.
      • deleted 9y ago
        [deleted]
      • gknoy 9y ago
        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 .
        • emodendroket 9y ago
          You can assign git aliases that execute shell commands by prefixing with an exclamation mark.
    • Ajedi32 9y ago
      Wouldn't work with commands like `git reset --hard` or `git checkout --force` though. Those commands delete uncommitted changes permanently.
  • falcolas 9y ago
    Only works for commits, but it's a very useful alias I've picked up. [alias] undo = reset HEAD~1 --mixed
  • postozoan 9y ago
    How about git uncommit? Undo suggests it might work for other actions like pushing
• mcaruso 9y ago
  My own personal top hit is: https://stackoverflow.com/questions/2003505/how-do-i-delete-a-git-branch-both-locally-and-remotely 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.
  • masklinn 9y ago
    TIL --delete, I still `git push origin :branchname`'d just this morning. Though at least now github provides easily access buttons.
  • Tarean 9y ago
    Gotta be honest, when I use git without tab completion for extended amounts of times I end up with a 'delete' branch eventually.
• INTPenis 9y ago
  That link was actually marked visited in my browser. Thank god for SO.
• Kiro 9y ago
  Why such a complicated top answer? There should be one command for this without involving esoteric stuff like HEAD, ~ and ...