This command deletes the last two commits, and all of your working files. For more cautious solutions, look further below.

The Git reset command will copy the last commit hash to a file called .git/ORIG_HEAD if you want to remind yourself of it another time:

git reset --hard HEAD~2

git reset --hard e291836

This command wipes out all your working files and the index, without affecting your commits:

git reset --hard

You can keep a backup in two ways. Firstly you can put a copy of your working files in stash:

git stash

And this command creates a new branch called my-rewind. It doesn't have the latest two commits on the main branch, but is otherwise the same.

So your main branch will continue to have those two commits, until you delete the branch later on. Much safer:

git checkout -b my-rewind HEAD~2

This can get you out of a lot of trouble. It won't replace any working files you've deleted, but this will roll back the last commands that have affected your branches.

It does this by telling the git reflog to go back to its penultimate state, thereby undoing the effect of the previous command you carried out, the reset on the branch.

It's an irony that the undo for a hard reset, is... a hard reset. In fact, this command can undo many actions that you take on a branch. Commits, check outs and cherry picks.

But for now, this will simply undo your branch reset action:

git reset --hard [email protected]{1}

But if you want to save the most time, try a free for any use Git client. It might be the best move you'll ever make with Git.