This command might cause losing commit history. To be on the safe side, have a backup of your git repo first.
When you don't want to keep the newer commit(s), go with the
git reset --hard CommitId && git clean -f
Get the commit Id by running the
git reflog command.
By now, you are done with your lical repository. Then, for updating your remote repository run the git command below:
git push -f
If the goal is to uncommit the last commit, then just use this command:
git reset HEAD~
Revert is the command to rollback the commits. To revert a particular commit, or a set of commits.
git revert --no-commit CommitId..HEADgit commit
In this command, you will need to include enough of the sha to identify the commit as unique among that repository: e.g.
git revert f688f767. By using
reflog you can have access to the list of commits and their SHAs.
This will return everything from the HEAD back to the commit hash, meaning it will restore that commit state in the working tree as if every commit after the reverting commit had been walked back. You can then commit the current tree, and it will create a brand new commit essentially the same to the commit you "reverted" to.
--no-commit flag lets git revert all the commits at once- otherwise you'll be prompted for a message for each commit in the range, littering your history with unnecessary new commits.
Other common gitrevisions are branch names followed by
~. For example,
git revert master~3 is 3 commits behind the head commit on the
If you don’t wish to change your commmit message, skip it by including the
--no-edit flag before the gitrevision:
git revert --no-edit master~3
.. between two gitrevisions:
git revert HEAD~4..HEAD~2
This will revert 3 commits: commit #2, #3 and #4.