git reset -hard pretends that everything since that hash didn't happen.git reflog tells you what you've had checked out, which is useful for undoing mistakes.Don't panic, you can use Git to essentially rewrite history.When things go wrong, make a backup before doing anything drastic!.Then they'll have to merge in their changes again. They can do the same thing: git checkout master to go to their local copy of the master branch, then git reset -hard to move it back to where it originally was, then git pull master to get the subsequent changes. Next up is the person who made the problematic commit. Now that repo's clean again, everyone else can pull from it and push to it again. This kind of thing can be dangerous if you're not sure what you're doing, so make sure you make a backup first! This simply pretends that everything since that commit didn't happen. If the remote server's a regular repo, not headless, then you can simply use git checkout master to make sure you're on the master branch, then git reset -hard to set it back to how it was. Use either method to find the hash of the last sensible commit. Other co-workers might also have in their repo a copy of this remote repo's master branch where it used to be, if they haven't pulled in the messy version. If you go to that particular machine, you can use git reflog to see where it was before this happened.

Next, ask that no one else push or pull until the repo you pushed to is neat and tidy again.

Rollback master git