#Git rollback last commit code#
#Git rollback last commit windows#

#Git rollback last commit code#

Why would you choose to do a revert over a reset operation? If you have already pushed your chain of commits to the remote repository (where others may have pulled your code and started working with it), a revert is a nicer way to cancel out changes for them. Reset to any previous commit: 1.git reset You can reset your head to previous commit or reset your head to previous any commit. If you want to just point to any previous commit use reset it points your local environment back to a previous commit. Or if the commit is a merge commit you can try this: 1.git revert -m 1 (-m 1 refers to the first parent of two merged branches) Or you can revert to any previous commit using the hash of that commit.Like: 1. If you REMOVE something in your file the revert process will ADD those file. If you want to REVERT all the changes from you last COMMIT that means If you ADD something in your file that will be REMOVED after revert has been done. Based on your requirement choose anything from below. ** Answering very shortly about revert and reset ** It is safe, will handle other's rebasing, and results in less unnecessary merges. I recommend making this the default behavior for pulling. r will preserve any merges they may have made. This will rewrite any of their local changes to master on top of the new rebased origin/master. Instead of a git fetch origin and git merge origin/master it will git fetch origin and git rebase -r origin/master. I recommend aliasing this as repush = push -force-with-lease. See –force considered harmful understanding git’s –force-with-lease. If someone else has already pushed your push will fail. git push -force-with-lease will only push your rebase if the repository is as you expect. If someone else has pushed changes they will be lost. Git push -f will indiscriminately replace the remote repository with your own changes. Here's an updated version of the procedure which is safer. push the 'revert' generated by git revert.git revert locally your last commit (creating a new commit that reverses what the previous commit did).Then I would suggest something that doesn't rewrite the history: What if somebody has already pulled the repo? What would I do then?

Using git push -force-with-lease ( that I present here, introduced in 2013 with Git 1.8.5) is safer. If the command with ' HEAD^' results in error no matches found: HEAD^, see ' git show HEAD^ doesn't seem to be working.

#Git rollback last commit windows#

Note, as commented by alien-technology in the comments below, on Windows (CMD session), you would need ^^: git reset -hard HEAD^^Īnd? as noted in the comments by Jon Schneider: (or, if you have direct access to the remote repo, you can change its HEAD reference even though it is a bare repo) If nobody has pulled your remote repo yet, you can change your branch HEAD and force push it to said remote repo: git reset -hard HEAD^