git revert commits a reverse change, so from the history point of view you will have two unnecessary commits that cancel each other. The {commit#} in your case should be the ID of the commit that you want to undo (= the last one). This should work as long as there are no other commits on top of it, otherwise you might get conflicts which require more work.

If you don't have any other commits apart from the one you want to undo, there is also a better way - simply move the branch back to point to the last commit you want to keep (= one before last).

Something like this (I assume you are working on master, that you didn't do revert yet and that there are no other people involved):

git checkout -b tmp_branch master~1
git branch -f master tmp_branch
git checkout master
git branch -D tmp_branch
git push -f origin master

And voilà. If your master is protected in GitHub, you will have to unprotect it. You can repeat this to go further back (or just use ~2, ~3 etc.)

Hello @dmastrop , hope this helps
First, to get rid of all the unstaged and uncommitted changes, you can use the following command:

git reset --hard HEAD

This will reset your working directory to the last commit, discarding all the changes you made since the last commit.

Now, to restore your state to a specific commit (7e73 in your case), you can use the following command:

git reset --hard 7e73

This will reset your working directory and move the HEAD to the specified commit, effectively restoring your state to that commit.

As for the revert command you mentioned:

git revert a05f341df1578822238d56d2777fdb230a2d8bba

This command will create a new commit that undoes the changes introduced by the specified commit (a05f341df1578822238d56d2777fdb230a2d8bba). However, since you want to get back to the state of the commit below (7e73) without creating any new commits, you don't need to use the revert command.

Remember, using git reset --hard and git revert can be powerful commands, so be cautious when using them. Always make sure you have a backup or have committed any important changes before running these commands.

If you ever need to get rid of unstaged and uncommitted stuff, the git reset --hard HEAD command should do the trick.

I hope this helps!

No, that feature isn't directly available on the GitHub web interface (as opposed to the "Revert" button recently added for GitHub for Mac/Windows)

Actually, it is for pull requests only, since June 24th, 2014:

Introducing the Revert Button

you can easily revert a pull request on GitHub by clicking Revert:

You'll be prompted to create a new pull request with the reverted changes:

git revert is a bit more complex to manage through the web as it can accept a range of commits.
It shouldn't be an issue in terms of collaboration though: a revert adds a new commit, it doesn't change the history of existing commits.