This-along with the idea that we can use either a hash ID or a name like HEAD or ARE-1195, or even the suffix trick like HEAD~2 or ARE-1195~2, wherever Git needs a hash ID-is basic how-to-work-with-Git knowledge that you should carry around in your head. Undo Commits Undo last commit putting everything back into the staging area: git reset -soft HEAD Add files and change message with: git commit -amend -m. Also, just as a quick reminder, git reset -hard will move the HEAD pointer back to the commit hash that was given, the Stage Index and the Working Directory will be reset back to the way they were at that commit, and all commits after the commit that was given will be dropped from the commit history. form like this, we give as hash the commit hash ID before the first commit we care about. Apart from the HEAD, you can also reset to other commits with the git reset -hard command. Deleting the commit in Git must be approached in one of two ways, depending on if you have or have not pushed your changes.

new-tip-commit can be a branch name (e.g., master, origin/master).

The image you included-which I will transform here into a new, different image-shows some of this: B-C-D-E. 11 Answers Sorted by: 1354 git branch -force

If new-tip-commit is omitted, it defaults to the current commit. To make sense of both, though, we should start with what a commit is and does for you. To perform a Git reset with the hard option in the CLI, you can run: git reset hard . Given a hash.txt with just 'a7abda785' as its contents (or any hash for that matter), you can run this batch file to do git reset using the hash from hash.txt: echo off set /p HASH < hash.txt git reset -hard HASH The /p sets the variable by prompting the user for input, which we automatically provide by redirecting the contents of the file.

Git's author (Linus Torvalds) unfortunately chose the wrong verb for at least one of these two actions: the one called revert should probably have been called backout (as it is in Mercurial). To jump back to a previous commit, first find the commits hash using git log.

After that, you have 2 options: If you plan to commit anything after that revision, I recommend you to checkout to a new branch: git checkout -b . git reset to commit hash

I tried looking for a possible solution and came across two terms, revert and reset but I'm confused between these. Use git log to find the revision you want to rollback to, and take note of the commit hash.

Git reset to commit hash