Once you are done with it then you are required to Push this commit forcefully by using + symbol in-front of branch as shown below. It is recommended that you ask all developers not to accept any pull requests on main remote branch. Run following to update your indexes (if there are any updates). Git status then you'll see that you are TWO Commits BEHIND from the remote branch as shown below These two commands clean force reset to commit stage 030bbf6 as shown below in snapshot

Perform the following steps to DELETE/REVERT Commits Locally+Remotelyįirst Locally Reverting to commit id 030bbf6 git reset -hard 030bbf6

If you also check remote (via Web Interface) then you can see that this would be same as shown belowĪs per screenshot currently you are on commit id e110322 however you want to revert back to 030bbf6 BOTH LOCALLY and REMOTELY. Run the following command to see the commit id that you want to revert git log -oneline -decorate -graph You can REVERT (or you can also call it DELETE) the Git Commit BOTH Locally and Remotely if you follow the steps as given below via git command line. So now HEAD is in the previous commit, both in local and remote: $ git log Since I don't want these changes, I just move the cursor back locally as well: $ git reset -hard b4zad078237fa48746a4feb6517fa409f6bf238e No changes added to commit (use 'git add' and/or 'git commit -a') ' to discard changes in working directory) Your branch is up-to-date with 'origin/my_new_branch'. Nice! Now I see the file that was changed on that commit ( myfile.py) shows in 'not staged for commit': $ git status I want to get rid of the last commit, which was already pushed, so I run: $ git push -f origin b4zad078237fa48746a4feb6517fa409f6bf238e:my_new_branch See a full example on a branch my_new_branch that I created for this purpose: $ git branch In the server, move the cursor back to the last known good commit: git push -f origin : Then you can fix the issue, create a new commit with the fix, and then push the new commits. Then your files are back to the state before the first revert. So your new revert commits will revert the previous revert commits. So what you would do, is to again execute the git revert command, but then with the range of commits of the revert commits. To re-apply the reverted commits, you have to revert the revert commits. After that you would want to re-apply the reverted commits locally, so your local repo's files are back to the state before the revert. Then push those revert commits, so the remote is stable. So then you would first do the git revert, as described before. Then you first want to restore the repo to a stable state, before you continue to fix the issue. Usually you revert commits because you discovered the commits that you pushed turn out to have an issue. Extra note for re-applying reverted commits:

Also, look at this answer for more information about reverting commits. Look at the git-revert man page for more information about the git revert command.

To find out the hash of the commit(s) you can use git log. You can always drop the latest revert commit (which reverts the oldest commit) with g reset -hard HEAD~. Some versions of git also revert the itself, so double check if that commit gets reverted or not. It reverts all the commits after up to and including. If you want to revert a range of commits, you can do it like this: git revert. Note that it only reverts that specific commit, and not commits that come after that. This will create a new commit which reverts the changes of the commit you specified. You can revert individual commits with: git revert

Discard changes git