Git Undo and Revert

‘revert’ is the command we use when we want to take a previous commit and add it as a new commit, keeping the log intact.
First thing, we need to find the point we want to return to. To do that, we need to go through the log. To avoid the very long log list, use the –oneline option which gives just one line per commit showing.
1. The first seven characters of the commit hash.
2. The commit message.

git log --oneline

We can revert the latest commit using ‘git revert HEAD’ (revert the latest change, and then commit). By adding the option –no-edit, we can skip the commit message editor (getting the default revert message).

git revert HEAD --no-edit

To revert to earlier commits, use ‘git revert HEAD~x’ (x being a number. 1 going back one more, 2 going back two more, etc.)
Command to go back by one commit

git revert HEAD~1

‘reset’ is the command we use when we want to move the repository back to a previous commit, discarding any changes made after that commit.
First, get the seven characters of the commit hash from the log for the commit that you want to go back for.
Then we reset our repository back to that specific commit using ‘git reset commithash’ (commithash being the first 7 characters of the commit hash we found in the log).

git reset 6199a6f

Even though the commits are no longer showing up in the log, it is not removed from Git. If we know the commit hash, we can reset to it using

git reset <commithash>

‘commit –amend’ is used to modify the most recent commit. It combines changes in the staging environment with the latest commit, and creates a new commit. This new commit replaces the latest commit entirely.
One of the simplest things you can do with –amend is to change a commit message

git commit --amend -m "Commit message here"

Adding files with ‘–amend’ works the same way as above. Just add them to the staging environment before committing.

git commit --amend