#this will preserve changes done to your files
git reset --soft HEAD~1
#this will get rid of the commit and the changes done to the files
$ git reset --hard HEAD~1
# Undo last commit.
# --soft flag makes sure that the changes in undone revisions are preserved.
# You'll find the changes as uncommitted local modifications in your working copy.
git reset --soft HEAD~1
# If you don't want to keep these changes, simply use the --hard flag.
# This will completely remove the changes.
git reset --hard HEAD~1
git reset HEAD~
$ git reset --hard HEAD~1
$ git commit -m "Something terribly misguided" # (0: Your Accident)
$ git reset HEAD~ # (1)
[ edit files as necessary ] # (2)
$ git add . # (3)
$ git commit -c ORIG_HEAD # (4)
git reset is the command responsible for the undo. It will undo your last commit while leaving your working tree (the state of your files on disk) untouched. You'll need to add them again before you can commit them again).
Make corrections to working tree files.
git add anything that you want to include in your new commit.
Commit the changes, reusing the old commit message. reset copied the old head to .git/ORIG_HEAD; commit with -c ORIG_HEAD will open an editor, which initially contains the log message from the old commit and allows you to edit it. If you do not need to edit the message, you could use the -C option.
Alternatively, to edit the previous commit (or just its commit message), commit --amend will add changes within the current index to the previous commit.
To remove (not revert) a commit that has been pushed to the server, rewriting history with git push origin main --force[-with-lease] is necessary. It's almost always a bad idea to use --force; prefer --force-with-lease instead, and as noted in the git manual:
You should understand the implications of rewriting history if you [rewrite history] has already been published.
Further Reading
You can use git reflog to determine the SHA-1 for the commit to which you wish to revert. Once you have this value, use the sequence of commands as explained above.
HEAD~ is the same as HEAD~1. The article What is the HEAD in git? is helpful if you want to uncommit multiple commits.
$ git commit -m "some comment"
$ git reset HEAD~
<< edit files as necessary >>
$ git add ...
$ git commit -c ORIG_HEAD
//the below code can recover your last commited files
git checkout -f
git revert <commit to revert>
git revert <commit hash of the commit to revert>
Code Example |
---|
Shell :: yarn react install |
Shell :: zsh: permission denied |
Shell :: how to check pyqt version |
Shell :: bash split variable by delimiter |
Shell :: Creating a directory or folder in linux |
Shell :: sudo windows |
Shell :: nasm compile windows 64 |
Shell :: spotify combo chercker |
Shell :: bash how to delete blank lines |
Shell :: list files of type txt from cmd |
Shell :: Flatpak in linux |
Shell :: octave ubuntu 20.04 |
Shell :: git force lf |
Shell :: brew update package |
Shell :: ignore file git |
Shell :: Flutter Git-Chrome-OS |
Shell :: linux remove link |
Shell :: what is the ssh credentials for minikube |
Shell :: delete all files in a directory command |
Shell :: kubernetes get statefulset |
Shell :: start xampp on mac |
Shell :: bash add help argument |
Shell :: boot pendrive cmd |
Shell :: gulp-gzip |
Shell :: where is my ubuntu folder located |
Shell :: removing a git folder |
Shell :: check all ruby version ubuntu |
Shell :: wsl start distro |
Shell :: ls permission |
Shell :: change name of branch github |