ℹ️ Skipped - page is already crawled
| Filter | Status | Condition | Details |
|---|---|---|---|
| HTTP status | PASS | download_http_code = 200 | HTTP 200 |
| Age cutoff | PASS | download_stamp > now() - 6 MONTH | 0.2 months ago |
| History drop | PASS | isNull(history_drop_reason) | No drop reason |
| Spam/ban | PASS | fh_dont_index != 1 AND ml_spam_score = 0 | ml_spam_score=0 |
| Canonical | PASS | meta_canonical IS NULL OR = '' OR = src_unparsed | Not set |
| Property | Value |
|---|---|
| URL | https://www.joehxblog.com/revert-an-older-commit-without-discarding-any-later-commits/ |
| Last Crawled | 2026-04-05 21:17:40 (6 days ago) |
| First Indexed | 2019-08-13 08:28:57 (6 years ago) |
| HTTP Status Code | 200 |
| Meta Title | Revert An Older Commit Without Discarding Any Later Commits – JoeHx Blog |
| Meta Description | After making a few changes to this blog in an attempt to appease Amazon and failing, I wanted to undo those changes. ... |
| Meta Canonical | null |
| Boilerpipe Text | This site utilizes Google Analytics, Google AdSense, as well as participates in affiliate partnerships with various companies including Amazon. Please view the
privacy policy
for more details.
After making a few changes to this blog in an attempt to
appease Amazon and failing
, I wanted to undo those changes. Thankfully, since this blog is hosted on GitHub pages, it’s versioned controlled via Git. Meaning I should easily be able to find the changes and undo them fairly easily.
In Git technical terms, I wanted to revert an older commit without discarding any later commits.
Some people might say you’re undoing a commit, which I guess is technically correct, but there’s also a reset command that brings a repository back to that commit.
First things first, I needed to find the individual commits I wanted to revert. This is where good commit messages would have come in handy - except I can be lazy when it comes to repos only I use.
Eventually, I found two commits I wanted to revert:
https://github.com/hendrixjoseph/hendrixjoseph.github.io/commit/7dc5ab44d430e6bd9e6ba02ee246fd764454186b
https://github.com/hendrixjoseph/hendrixjoseph.github.io/commit/461914ecb7a057013c0a486b0f445c44bef4bdb9
The nice thing about having two commits I wanted to revert is that I could do one via the
TortoiseGit
GUI and one via the command line.
Revert an Older Commit Via the TortioseGit GUI
Make a backup of the directory - i.e. just make a copy in the same directory:
Open the Git Log by right-clicking on the Git directory and selecting
TortoiseGit → Show log
:
Scroll through and find the commit to revert (and double check that its hash is the same), right-click on it and select
Revert change by this commit
:
At this point, most people would have successfully reverted their commit. I, however, got a “Failed Revert” dialog that said “error: could not revert”:
It wasn’t all bad, though. For the most part, my revert
did
happen, it just wasn’t able to auto-commit after the revert due to a conflict with a later commit. I simply navigated through the Git directory in my file system and solved the conflict.
Revert an Older Commit Via the Git Bash Command Line
Now for the next commit undo, which I wanted to do via the command line.
To reach the Git command line, I just right-clicked on the Git directory and selected
Git Bash Here
(look at the image on step two above to see where it’s located). The Git command to revert a specific command is straightforward:
git revert <commit hash>
The commit hash is that last bit of numbers and letters in the GitHub commit url. So the command I typed was:
git revert 461914ecb7a057013c0a486b0f445c44bef4bdb9
The revert was successful, and it did autocommit successfully as well (there were no conflicts). Being Git, I did have to push manually.
If I didn’t want to auto-commit, I would simply have to supply the
--no-commit
or
-n
flags:
git revert --no-commit <commit hash>
git revert -n <commit hash>
Here are the links to the revert commits on GitHub if you’re wondering what they look like (spoiler: nothing special):
https://github.com/hendrixjoseph/hendrixjoseph.github.io/commit/a9315e6d67ac3f67dac717f5e0ba6196fa434f13
https://github.com/hendrixjoseph/hendrixjoseph.github.io/commit/edf52d6d85a64d0011b6fd5d54f361d533b94d68
Sources
How can I undo an older commit?
Stackoverflow: Undo a particular commit in Git that’s been pushed to remote repos |
| Markdown | [](https://www.joehxblog.com/)
[JoeHx Blog](https://www.joehxblog.com/)
Writing What I Want
[Home](https://www.joehxblog.com/)\|[About](https://www.joehxblog.com/about/)\|[Work with Me](https://www.joehxblog.com/work-with-me/)\|[T-Shirts](https://www.joehxtees.com/)
# [Revert An Older Commit Without Discarding Any Later Commits](https://www.joehxblog.com/revert-an-older-commit-without-discarding-any-later-commits/)
[share](https://www.facebook.com/dialog/share?app_id=197946313591875&display=page&href=https://www.joehxblog.com/revert-an-older-commit-without-discarding-any-later-commits/)
[tweet](https://twitter.com/intent/tweet?url=https://www.joehxblog.com/revert-an-older-commit-without-discarding-any-later-commits/&via=JoeHxBlog&text=Revert+An+Older+Commit+Without+Discarding+Any+Later+Commits)
[share](https://www.linkedin.com/shareArticle?url=https://www.joehxblog.com/revert-an-older-commit-without-discarding-any-later-commits/&source=JoeHx%20Blog)
[share](https://www.reddit.com/submit?url=https://www.joehxblog.com/revert-an-older-commit-without-discarding-any-later-commits/)
***
February 26, 2019
[git](https://www.joehxblog.com/tags/#git)\|[github](https://www.joehxblog.com/tags/#github)
***
*This site utilizes Google Analytics, Google AdSense, as well as participates in affiliate partnerships with various companies including Amazon. Please view the [privacy policy](https://www.joehxblog.com/privacy/) for more details.*
After making a few changes to this blog in an attempt to [appease Amazon and failing](https://www.joehxblog.com/amazon-shut-down-my-associate-account/), I wanted to undo those changes. Thankfully, since this blog is hosted on GitHub pages, it’s versioned controlled via Git. Meaning I should easily be able to find the changes and undo them fairly easily.
In Git technical terms, I wanted to revert an older commit without discarding any later commits.
Some people might say you’re undoing a commit, which I guess is technically correct, but there’s also a reset command that brings a repository back to that commit.
First things first, I needed to find the individual commits I wanted to revert. This is where good commit messages would have come in handy - except I can be lazy when it comes to repos only I use.
Eventually, I found two commits I wanted to revert:
- <https://github.com/hendrixjoseph/hendrixjoseph.github.io/commit/7dc5ab44d430e6bd9e6ba02ee246fd764454186b>
- <https://github.com/hendrixjoseph/hendrixjoseph.github.io/commit/461914ecb7a057013c0a486b0f445c44bef4bdb9>
The nice thing about having two commits I wanted to revert is that I could do one via the [TortoiseGit](https://tortoisegit.org/) GUI and one via the command line.
## Revert an Older Commit Via the TortioseGit GUI
1. Make a backup of the directory - i.e. just make a copy in the same directory:
1. Open the Git Log by right-clicking on the Git directory and selecting **TortoiseGit → Show log**:
1. Scroll through and find the commit to revert (and double check that its hash is the same), right-click on it and select **Revert change by this commit**:
At this point, most people would have successfully reverted their commit. I, however, got a “Failed Revert” dialog that said “error: could not revert”:
It wasn’t all bad, though. For the most part, my revert *did* happen, it just wasn’t able to auto-commit after the revert due to a conflict with a later commit. I simply navigated through the Git directory in my file system and solved the conflict.
## Revert an Older Commit Via the Git Bash Command Line
Now for the next commit undo, which I wanted to do via the command line.
To reach the Git command line, I just right-clicked on the Git directory and selected **Git Bash Here** (look at the image on step two above to see where it’s located). The Git command to revert a specific command is straightforward:
```
git revert <commit hash>
```
The commit hash is that last bit of numbers and letters in the GitHub commit url. So the command I typed was:
```
git revert 461914ecb7a057013c0a486b0f445c44bef4bdb9
```
The revert was successful, and it did autocommit successfully as well (there were no conflicts). Being Git, I did have to push manually.
If I didn’t want to auto-commit, I would simply have to supply the `--no-commit` or `-n` flags:
```
git revert --no-commit <commit hash>
git revert -n <commit hash>
```
Here are the links to the revert commits on GitHub if you’re wondering what they look like (spoiler: nothing special):
- <https://github.com/hendrixjoseph/hendrixjoseph.github.io/commit/a9315e6d67ac3f67dac717f5e0ba6196fa434f13>
- <https://github.com/hendrixjoseph/hendrixjoseph.github.io/commit/edf52d6d85a64d0011b6fd5d54f361d533b94d68>
## Sources
- [How can I undo an older commit?](https://www.git-tower.com/learn/git/faq/undo-revert-old-commit)
- [Stackoverflow: Undo a particular commit in Git that’s been pushed to remote repos](https://stackoverflow.com/questions/2318777/undo-a-particular-commit-in-git-thats-been-pushed-to-remote-repos)
Previous Post: [Amazon Shut Down My Associate Account](https://www.joehxblog.com/amazon-shut-down-my-associate-account/)
Next Post: [Example Schedule C for Cryptocurrency Mining](https://www.joehxblog.com/example-schedule-c-for-cryptocurrency-mining/)
Next git Post: [Questions on Branches and Rebases in Git](https://www.joehxblog.com/questions-on-branches-and-rebases-in-git/)
Next github Post: [3 Ways to Create New Directories in the GitHub Web Interface](https://www.joehxblog.com/3-ways-to-create-new-directories-in-the-github-web-interface/)
### Leave a Reply
Thank you. Your comment will be visible after approval.
Your comment has been submitted, but their seems to be an error. Check your browser console for more details.
I am Joe. I'm one of many Joes, but I am uniquely me. I'm the messiest organized guy you'll ever meet. My glasses are always bent and my hair always a mess. I've never had a role model and as such am my own person. Scientist, programmer, Christian, libertarian, and life long learner.
Latest post from March 30, 2026: [A Poké Ball for My Son's Birthday](https://www.joehxblog.com/a-pokeball-for-my-sons-birthday/) [](https://www.joehxblog.com/a-pokeball-for-my-sons-birthday/)
[](https://github.com/hendrixjoseph "GitHub Profile") [](https://www.reddit.com/user/joehx/ "Reddit Profile") [](https://twitter.com/intent/user?screen_name=JoeHxBlog "Follow me on Twitter")
[RSS feed](https://www.joehxblog.com/feed.xml "Subscribe to my RSS feed")
[Like](https://www.facebook.com/JoeHxBlog "Like me on Facebook")
[](https://affiliates.abebooks.com/c/2462910/76887/2029)
© 2026 Joseph Hendrix
Joe around the web: [Facebook](https://www.facebook.com/JoeHxBlog) [Twitter](https://www.twitter.com/JoeHxBlog) [GitHub](https://github.com/hendrixjoseph) [LinkedIn](https://www.linkedin.com/in/joehx) [Wikipedia](https://en.wikipedia.org/wiki/User:Hendrixjoseph) [Wright State](http://people.wright.edu/hendrix.11) [Bloglovin](https://www.bloglovin.com/blog/18787949/?claim=wdwd7egbcxx) [Mix](https://mix.com/joehx) Website Sections: [Privacy Policy](https://www.joehxblog.com/privacy/) [Referral Links](https://www.joehxblog.com/referral/) [Web Portfolio](https://www.joehxblog.com/web-portfolio/) [Featured](https://www.joehxblog.com/featured/) [Post Statistics](https://www.joehxblog.com/statistics/) [Tags](https://www.joehxblog.com/tags/) [Sitemap](https://www.joehxblog.com/sitemap/) Tools: [Amazon Keyword Search Generator](https://www.joehxblog.com/tools/amazon-keyword-search-generator/)[Calorie to Exercise Calculator](https://www.joehxblog.com/tools/calorie-to-exercise-calculator/)[Compound Interest Calculator](https://www.joehxblog.com/tools/compound-interest-calculator/)[Ohio Sample Ballot Links by County](https://www.joehxblog.com/tools/ohio-sample-ballot-links-by-county/)[Temperature Conversion](https://www.joehxblog.com/tools/temperature-conversion/)[URL Decoder & Encoder](https://www.joehxblog.com/tools/url-decoder-encoder/)
[](https://validator.w3.org/nu/?doc=https%3A%2F%2Fwww.joehxblog.com%2Frevert-an-older-commit-without-discarding-any-later-commits%2F) |
| Readable Markdown | ***
***
*This site utilizes Google Analytics, Google AdSense, as well as participates in affiliate partnerships with various companies including Amazon. Please view the [privacy policy](https://www.joehxblog.com/privacy/) for more details.*
After making a few changes to this blog in an attempt to [appease Amazon and failing](https://www.joehxblog.com/amazon-shut-down-my-associate-account/), I wanted to undo those changes. Thankfully, since this blog is hosted on GitHub pages, it’s versioned controlled via Git. Meaning I should easily be able to find the changes and undo them fairly easily.
In Git technical terms, I wanted to revert an older commit without discarding any later commits.
Some people might say you’re undoing a commit, which I guess is technically correct, but there’s also a reset command that brings a repository back to that commit.
First things first, I needed to find the individual commits I wanted to revert. This is where good commit messages would have come in handy - except I can be lazy when it comes to repos only I use.
Eventually, I found two commits I wanted to revert:
- <https://github.com/hendrixjoseph/hendrixjoseph.github.io/commit/7dc5ab44d430e6bd9e6ba02ee246fd764454186b>
- <https://github.com/hendrixjoseph/hendrixjoseph.github.io/commit/461914ecb7a057013c0a486b0f445c44bef4bdb9>
The nice thing about having two commits I wanted to revert is that I could do one via the [TortoiseGit](https://tortoisegit.org/) GUI and one via the command line.
## Revert an Older Commit Via the TortioseGit GUI
1. Make a backup of the directory - i.e. just make a copy in the same directory:
1. Open the Git Log by right-clicking on the Git directory and selecting **TortoiseGit → Show log**:
1. Scroll through and find the commit to revert (and double check that its hash is the same), right-click on it and select **Revert change by this commit**:
At this point, most people would have successfully reverted their commit. I, however, got a “Failed Revert” dialog that said “error: could not revert”:
It wasn’t all bad, though. For the most part, my revert *did* happen, it just wasn’t able to auto-commit after the revert due to a conflict with a later commit. I simply navigated through the Git directory in my file system and solved the conflict.
## Revert an Older Commit Via the Git Bash Command Line
Now for the next commit undo, which I wanted to do via the command line.
To reach the Git command line, I just right-clicked on the Git directory and selected **Git Bash Here** (look at the image on step two above to see where it’s located). The Git command to revert a specific command is straightforward:
```
git revert <commit hash>
```
The commit hash is that last bit of numbers and letters in the GitHub commit url. So the command I typed was:
```
git revert 461914ecb7a057013c0a486b0f445c44bef4bdb9
```
The revert was successful, and it did autocommit successfully as well (there were no conflicts). Being Git, I did have to push manually.
If I didn’t want to auto-commit, I would simply have to supply the `--no-commit` or `-n` flags:
```
git revert --no-commit <commit hash>
git revert -n <commit hash>
```
Here are the links to the revert commits on GitHub if you’re wondering what they look like (spoiler: nothing special):
- <https://github.com/hendrixjoseph/hendrixjoseph.github.io/commit/a9315e6d67ac3f67dac717f5e0ba6196fa434f13>
- <https://github.com/hendrixjoseph/hendrixjoseph.github.io/commit/edf52d6d85a64d0011b6fd5d54f361d533b94d68>
## Sources
- [How can I undo an older commit?](https://www.git-tower.com/learn/git/faq/undo-revert-old-commit)
- [Stackoverflow: Undo a particular commit in Git that’s been pushed to remote repos](https://stackoverflow.com/questions/2318777/undo-a-particular-commit-in-git-thats-been-pushed-to-remote-repos) |
| Shard | 10 (laksa) |
| Root Hash | 2987447414847851410 |
| Unparsed URL | com,joehxblog!www,/revert-an-older-commit-without-discarding-any-later-commits/ s443 |