First, let\u2019s talk about what a commit<\/strong> really is.<\/p>\n A commit is like a save point in your project\u2019s timeline. Think of it as a snapshot. Each time you commit, Git takes a picture of your files at that moment. If something goes wrong later, you can rewind to one of those snapshots.<\/p>\n Pretty cool, right?<\/p>\n But here\u2019s where things get tricky. There isn\u2019t just one way to \u201cgo back.\u201d There are multiple ways. Each one does something slightly different. Choosing the wrong one can confuse your team. Or worse, rewrite history in a bad way.<\/p>\n Let\u2019s break it down.<\/p>\n This is your safest choice. Especially if you already pushed your changes to GitHub.<\/p>\n The command looks like this:<\/p>\n What does this do?<\/p>\n It creates a new<\/em> commit that undoes the changes from the previous commit. It doesn\u2019t delete history. It doesn\u2019t hide anything. It simply adds another snapshot that reverses the bad one.<\/p>\n Think of it like saying:<\/p>\n \u201cOops, that was a mistake. Here is a new commit that fixes it.\u201d<\/em><\/p>\n That\u2019s why teams love git revert<\/strong>. It keeps everything transparent.<\/p>\n How do you find the commit hash? Easy.<\/p>\n You\u2019ll see a list of commits. Each one has a long string of characters. That\u2019s your commit hash.<\/p>\n Copy it. Paste it into the revert command. Done.<\/p>\n Then push your changes:<\/p>\n And breathe again.<\/p>\n Now things get interesting.<\/p>\n git reset<\/strong> actually moves your branch pointer backward. It\u2019s more powerful. But also more dangerous.<\/p>\n The command:<\/p>\n This tells Git:<\/p>\n \u201cTake me back to this exact moment. Forget everything after it.\u201d<\/em><\/p>\n And Git listens.<\/p>\n There are three main reset modes:<\/p>\n –hard<\/strong> is the dramatic one. It wipes out changes in both staging and working directory.<\/p>\n Be careful.<\/p>\n If you already pushed the commits and then run reset locally, you\u2019ll need to force push:<\/p>\n This rewrites history on GitHub.<\/p>\n Your teammates may not be amused.<\/p>\n So use force push sparingly.<\/p>\n Sometimes things go very wrong. Maybe a feature branch turned into a monster. No worries.<\/p>\n You can reset the branch to an earlier commit and then push safely using:<\/p>\n This is safer than It checks if someone else made changes before overwriting anything. Think of it as polite force pushing.<\/p>\n You don\u2019t always need the command line.<\/p>\n On GitHub\u2019s website, you can revert commits directly.<\/p>\n Here\u2019s how:<\/p>\n This creates a new commit that reverses the old one. Just like git revert<\/em>.<\/p>\n It\u2019s simple. Visual. Clean.<\/p>\n Before doing anything dramatic, create a backup branch.<\/p>\n This saves your current state.<\/p>\n If something goes wrong, you can return to it.<\/p>\n It takes five seconds. It saves hours of stress.<\/p>\n Let\u2019s save you some pain.<\/p>\n And very important:<\/p>\n Always run:<\/p>\n before and after changes.<\/p>\n It tells you what\u2019s happening. It\u2019s your compass.<\/p>\n Yes. That happens.<\/p>\n Good news: Git tracks everything.<\/p>\n You can use:<\/p>\n This shows a log of where HEAD has been. Even movements caused by reset.<\/p>\n You can recover almost anything from here.<\/p>\n Git is like that friend who remembers everything. Even what you wish it didn\u2019t.<\/p>\n If you\u2019re ever unsure, choose revert<\/strong>.<\/p>\n It\u2019s the grown-up answer.<\/p>\n Let\u2019s say your last three commits were:<\/p>\n![\"\"](\"https:\/\/savethevideo.net\/blog\/wp-content\/uploads\/2026\/02\/black-flat-screen-computer-monitor-git-commit-graph-timeline-version-control-history-branching-diagram-1.jpg\")
\nOption 1: Revert a Commit (The Safe Way)<\/strong><\/h2>\n
\n
git revert <commit-hash><\/code><\/li>\n<\/ul>\nWhen Should You Use git revert?<\/strong><\/h3>\n
\n
\n
git log<\/code><\/li>\n<\/ul>\n\n
git push<\/code><\/li>\n<\/ul>\nOption 2: Reset to an Earlier Commit (The Risky Way)<\/strong><\/h2>\n
\n
git reset --hard <commit-hash><\/code><\/li>\n<\/ul>\n![\"\"](\"https:\/\/savethevideo.net\/blog\/wp-content\/uploads\/2026\/02\/turned-on-macbook-pro-developer-at-computer-undoing-code-git-reset-concept-illustration-version-rollback-interface.jpg\")
\n\n
When Should You Use git reset?<\/strong><\/h3>\n
\n
\n
git push --force<\/code><\/li>\n<\/ul>\nOption 3: Revert a Whole Branch to a Previous State<\/strong><\/h2>\n
\n
git push --force-with-lease<\/code><\/li>\n<\/ul>\n--force<\/code>.<\/p>\nHow to Do It Directly on GitHub<\/strong><\/h2>\n
\n
![\"\"](\"https:\/\/savethevideo.net\/blog\/wp-content\/uploads\/2026\/02\/github-website-on-desktop-github-interface-commit-history-page-revert-button-on-github-pull-request-creation-screen.jpg\")
\nPro Tip: Create a Backup Branch First<\/strong><\/h2>\n
\n
git branch backup-before-revert<\/code><\/li>\n<\/ul>\nCommon Mistakes to Avoid<\/strong><\/h2>\n
\n
\n
git status<\/code><\/li>\n<\/ul>\nWhat If You Reverted the Wrong Commit?<\/strong><\/h2>\n
\n
git reflog<\/code><\/li>\n<\/ul>\nRevert vs Reset: Quick Comparison<\/strong><\/h2>\n
\n
A Simple Real-Life Example<\/strong><\/h2>\n