🕷️ Crawler Inspector

URL Lookup

Direct Parameter Lookup

Raw Queries and Responses

1. Shard Calculation

Query:

Response:

Calculated Shard: 147 (from laksa099)

2. Crawled Status Check

Query:

curl -X POST \
  'http://laksa147.int.ahrefs:8124/' \
  -H 'Content-Type: text/plain' \
  -H 'X-ClickHouse-Database: crawler3' \
  -H 'Authorization: Basic YXBpOg==' \
  -d 'SELECT getAhrefsURLFromUnparsed(src_unparsed) AS found_url, ifNull(toUnixTimestamp(download_stamp), 0) AS crawl_time, ifNull(toUnixTimestamp(props_url_first_seen), 0) AS first_indexed_time, download_http_code AS http_code, src_unparsed AS src_unparsed, src_root_hash AS src_root_hash, history_drop_reason AS history_drop_reason, meta_title AS meta_title, meta_descriptions AS meta_descriptions, attrs_boilerpipe_text AS attrs_boilerpipe_text, attrs_markdown AS attrs_markdown, attrs_readable_markdown AS attrs_readable_markdown, meta_canonical AS meta_canonical FROM crawler3.page_info_local FINAL PREWHERE (src_root_hash, src_unparsed) IN ((getAhrefsRootHashFromUnparsed(getAhrefsUnparsedNoserviceFromURL(\'https://sentry.io/answers/undo-the-most-recent-local-git-commits/\')), getAhrefsUnparsedNoserviceFromURL(\'https://sentry.io/answers/undo-the-most-recent-local-git-commits/\'))) FORMAT JSONEachRow'

Response:

{"found_url":"https:\/\/sentry.io\/answers\/undo-the-most-recent-local-git-commits\/","crawl_time":1775619024,"first_indexed_time":1687330058,"http_code":200,"src_unparsed":"io,sentry!\/answers\/undo-the-most-recent-local-git-commits\/ s443","src_root_hash":"17800916657557307547","history_drop_reason":null,"meta_title":"Undo the most recent local Git commits | Sentry","meta_descriptions":["Sentry helps developers monitor and fix crashes in real time. Get the details you need to resolve the most important issues quickly."],"attrs_boilerpipe_text":"The Problem\nHow do I undo the most recent local commits in Git?\nThe Solution\nThe\ngit reset\ncommand will return the current branch to a specified previous commit. By default, this command will remove commits from the current branch’s history while leaving the files in the working tree untouched. This allows you to redo one or more commits without losing any work.\nWhen calling\ngit reset\n, you need to specify the commit to reset to. You can get the hash of the commit you want from\ngit log\n, or you can specify an ancestor of\nHEAD\n, the current commit, using the\ntilde (~) suffix\n. The following commands will undo and redo the most recent commit:\ngit\nadd\n.\ngit\ncommit\n-m\n\"This commit is a mistake\"\ngit\nreset HEAD~\ngit\nadd\nmain.py\n# need to re-add files after reset\ngit\ncommit\n-m\n\"This commit corrects the mistake\"\nTo undo the last two commits, use the commands:\ngit\nadd\n.\ngit\ncommit\n-m\n\"This commit is a mistake\"\n# make changes\ngit\nadd\n.\ngit\ncommit\n-m\n\"This commit is another mistake\"\ngit\nreset HEAD~2\ngit\nadd\n.\ngit\ncommit\n-m\n\"this commit corrects both mistakes\"\nIf you don’t want to have to re-stage your files after a reset, you can use the\n--soft\nflag:\ngit\nadd\n.\ngit\ncommit\n-m\n\"This commit is a mistake\"\ngit\nreset\n--soft\nHEAD~\n# no need to git add, as files are already staged\ngit\ncommit\n-m\n\"This commit corrects the mistake\"\nIf you want to reset both the Git history and the working tree to the state of a previous commit, you can use the\n--hard\nflag. Note that this will reverse all changes made to tracked files, including ones that haven’t yet been committed.\ngit\nadd\n.\ngit\ncommit\n-m\n\"\"\ngit\nreset\n--hard\nHEAD~\ngit reset --hard\nshould be used with caution. However, you can still retrieve any deleted commits using\ngit reflog\n,\nup to 90 days\nafter they were deleted. When run,\ngit reflog\nwill show a list of commits previously on the tips of branches. From this list, you can pick out the partial hash of the commit (e.g.\n5c8f5a7\n) to restore and create a new branch for it:\ngit\ncheckout\n-b\nrestored-commit-branch 5c8f5a7\nIf you would like to preserve your repository’s history but return the files to a previous state, you can use\ngit revert\nto create new commits that do the opposite of existing commits, i.e. removing lines and files that were added and adding lines and files that were removed:\ngit\nadd\n.\ngit\ncommit\n-m\n\"This commit is a mistake\"\ngit\nrevert HEAD\n# will create a new commit doing the opposite of the one above\nFor more on\ngit revert\n, see our answer for\nreverting to a previous commit\n.\nFurther Reading\nIf you’re looking to get a deeper understanding of how web performance optimization works, take a look at the following articles:\nFrom LCP to CLS: Improve your Core Web Vitals with Image Loading Best Practices\nHow to identify and fix Render-Blocking Resources\nLow effort image optimization tips\n5 easy tips to improve your personal website performance\nHow to hack your Google Lighthouse scores in 2024","attrs_markdown":"[Skip to main content](https:\/\/sentry.io\/answers\/undo-the-most-recent-local-git-commits\/#main-content)\n\nMenu\n\nPlatform\n\nProducts\n\n- [Error Monitoring](https:\/\/sentry.io\/product\/error-monitoring\/)\n- [Logs](https:\/\/sentry.io\/product\/logs\/)\n- [Session Replay](https:\/\/sentry.io\/product\/session-replay\/)\n- [Tracing](https:\/\/sentry.io\/product\/tracing\/)\n- [Seer NEW](https:\/\/sentry.io\/product\/seer\/)\n- [Profiling](https:\/\/sentry.io\/product\/profiling\/)\n- [AI Code Review NEW](https:\/\/sentry.io\/product\/seer\/ai-code-review\/)\n- [Size Analysis NEW](https:\/\/sentry.io\/product\/size-analysis)\n- [Cron Monitoring](https:\/\/sentry.io\/product\/cron-monitoring\/)\n- [Uptime Monitoring](https:\/\/sentry.io\/product\/uptime-monitoring\/)\n- [Sentry CLI NEW](https:\/\/cli.sentry.dev\/)\n\nIntegrations\n\n- [![](https:\/\/sentry.io\/astro-assets\/nav-icons\/github.png)Github](https:\/\/sentry.io\/integrations\/github\/)\n- [![](https:\/\/sentry.io\/astro-assets\/nav-icons\/slack.png)Slack](https:\/\/sentry.io\/integrations\/slack\/)\n- [Sentry MCP NEW](https:\/\/mcp.sentry.dev\/)\n- [All Integrations](https:\/\/sentry.io\/integrations\/)\n\nSDKs\n\n- [![](https:\/\/sentry.io\/astro-assets\/nav-icons\/javascript.png)Javascript](https:\/\/sentry.io\/for\/javascript\/)\n- [![](https:\/\/sentry.io\/astro-assets\/nav-icons\/python.png)Python](https:\/\/sentry.io\/for\/python\/)\n- [![](https:\/\/sentry.io\/astro-assets\/nav-icons\/react.png)React](https:\/\/sentry.io\/for\/react\/)\n- [![](https:\/\/sentry.io\/astro-assets\/nav-icons\/laravel.png)Laravel](https:\/\/sentry.io\/for\/laravel\/)\n- [![](https:\/\/sentry.io\/astro-assets\/nav-icons\/nextjs.png)Next.js](https:\/\/sentry.io\/for\/nextjs\/)\n- [All SDKs](https:\/\/sentry.io\/platforms\/)\n\nSolutions\n\n### Solutions\n- [Web \/ Full Stack Development](https:\/\/sentry.io\/for\/full-stack\/)\n- [Mobile Crash Reporting](https:\/\/sentry.io\/solutions\/mobile-developers\/)\n- [Game Crash Reporting](https:\/\/sentry.io\/solutions\/game-developers\/)\n- [AI Observability](https:\/\/sentry.io\/solutions\/ai-observability\/)\n- [Application Performance Monitoring](https:\/\/sentry.io\/solutions\/application-performance-monitoring\/)\n- [Real User Monitoring](https:\/\/sentry.io\/solutions\/real-user-monitoring-rum\/)\n- [Ecommerce](https:\/\/sentry.io\/solutions\/ecommerce\/)\n- [Enterprise](https:\/\/sentry.io\/for\/enterprise\/)\n- [Startups](https:\/\/sentry.io\/for\/startups\/)\n\nResources\n\nLearn\n\n- [Blog](https:\/\/blog.sentry.io\/)\n- [Changelog](https:\/\/sentry.io\/changelog\/)\n- [Sandbox](https:\/\/sandbox.sentry.io\/)\n- [Resources](https:\/\/sentry.io\/resources\/)\n- [Syntax](https:\/\/syntax.fm\/)\n- [Customers](https:\/\/sentry.io\/customers\/)\n- [Cookbook](https:\/\/sentry.io\/cookbook\/)\n\nSupport\n\n- [Contact Us](https:\/\/sentry.io\/contact\/enterprise\/)\n- [Help Center](https:\/\/help.sentry.io\/)\n- [Status](https:\/\/status.sentry.io\/)\n\nHang out with us\n\n- [Sentry Build](https:\/\/sentry.io\/resources\/sentry-build\/)\n- [Events](https:\/\/sentry.io\/events\/)\n- [Merch](https:\/\/sentry.shop\/)\n\n[Docs](https:\/\/docs.sentry.io\/)\n\n[Pricing](https:\/\/sentry.io\/pricing\/)\n\n[Sign In](https:\/\/sentry.io\/auth\/login\/)   [Get Demo](https:\/\/sentry.io\/demo\/)   [Get Started](https:\/\/sentry.io\/signup\/)\n\n- Platform\n- Solutions\n  - [Web \/ Full Stack Development](https:\/\/sentry.io\/for\/full-stack\/)\n  - [Mobile Crash Reporting](https:\/\/sentry.io\/solutions\/mobile-developers\/)\n  - [Game Crash Reporting](https:\/\/sentry.io\/solutions\/game-developers\/)\n  - [AI Observability](https:\/\/sentry.io\/solutions\/ai-observability\/)\n  - [Application Performance Monitoring](https:\/\/sentry.io\/solutions\/application-performance-monitoring\/)\n  - [Real User Monitoring](https:\/\/sentry.io\/solutions\/real-user-monitoring-rum\/)\n  - [Ecommerce](https:\/\/sentry.io\/solutions\/ecommerce\/)\n  - [Enterprise](https:\/\/sentry.io\/for\/enterprise\/)\n  - [Startups](https:\/\/sentry.io\/for\/startups\/)\n- Resources\n- [Docs](https:\/\/docs.sentry.io\/)\n- [Pricing](https:\/\/sentry.io\/pricing\/)\n\n[Sign In](https:\/\/sentry.io\/auth\/login\/)   [Get Demo](https:\/\/sentry.io\/demo\/)   [Get Started](https:\/\/sentry.io\/signup\/)\n\n[Sentry Answers](https:\/\/sentry.io\/answers\/) \\> [Git](https:\/\/sentry.io\/answers\/git\/) \\> Undo the most recent local Git commits\n\n# Undo the most recent local Git commits\n![](https:\/\/sentry.io\/astro-assets\/legacy\/ghost.png)\n\nDavid Y. —\n\nFebruary 15, 2023\n\n[jump to solution](https:\/\/sentry.io\/answers\/undo-the-most-recent-local-git-commits\/#the-solution)\n\n## The Problem\nHow do I undo the most recent local commits in Git?\n\n## The Solution\nThe [`git reset`](https:\/\/git-scm.com\/docs\/git-reset) command will return the current branch to a specified previous commit. By default, this command will remove commits from the current branch’s history while leaving the files in the working tree untouched. This allows you to redo one or more commits without losing any work.\n\nWhen calling `git reset`, you need to specify the commit to reset to. You can get the hash of the commit you want from `git log`, or you can specify an ancestor of `HEAD`, the current commit, using the [tilde (~) suffix](https:\/\/git-scm.com\/docs\/git-rev-parse#Documentation\/git-rev-parse.txt-emltrevgtltngtemegemHEADmaster3em). The following commands will undo and redo the most recent commit:\n```\ngit add .\ngit commit -m \"This commit is a mistake\"\ngit reset HEAD~\ngit add main.py # need to re-add files after reset\ngit commit -m \"This commit corrects the mistake\"\n```\nTo undo the last two commits, use the commands:\n```\ngit add .\ngit commit -m \"This commit is a mistake\"\n# make changes\ngit add .\ngit commit -m \"This commit is another mistake\"\ngit reset HEAD~2\ngit add .\ngit commit -m \"this commit corrects both mistakes\"\n```\nIf you don’t want to have to re-stage your files after a reset, you can use the `--soft` flag:\n```\ngit add .\ngit commit -m \"This commit is a mistake\"\ngit reset --soft HEAD~\n# no need to git add, as files are already staged\ngit commit -m \"This commit corrects the mistake\"\n```\nIf you want to reset both the Git history and the working tree to the state of a previous commit, you can use the `--hard` flag. Note that this will reverse all changes made to tracked files, including ones that haven’t yet been committed.\n```\ngit add .\ngit commit -m \"\"\ngit reset --hard HEAD~\n```\n`git reset --hard` should be used with caution. However, you can still retrieve any deleted commits using [`git reflog`](https:\/\/git-scm.com\/docs\/git-reflog), [up to 90 days](https:\/\/git-scm.com\/docs\/git-reflog#Documentation\/git-reflog.txt---expirelttimegt) after they were deleted. When run, `git reflog` will show a list of commits previously on the tips of branches. From this list, you can pick out the partial hash of the commit (e.g. `5c8f5a7`) to restore and create a new branch for it:\n```\ngit checkout -b restored-commit-branch 5c8f5a7\n```\nIf you would like to preserve your repository’s history but return the files to a previous state, you can use `git revert` to create new commits that do the opposite of existing commits, i.e. removing lines and files that were added and adding lines and files that were removed:\n```\ngit add .\ngit commit -m \"This commit is a mistake\"\ngit revert HEAD # will create a new commit doing the opposite of the one above\n```\nFor more on `git revert`, see our answer for [reverting to a previous commit](https:\/\/sentry.io\/answers\/revert-a-git-repository-to-a-previous-commit\/).\n\n## Further Reading\nIf you’re looking to get a deeper understanding of how web performance optimization works, take a look at the following articles:\n\n- [From LCP to CLS: Improve your Core Web Vitals with Image Loading Best Practices](https:\/\/blog.sentry.io\/from-lcp-to-cls-improve-your-core-web-vitals-with-image-loading-best\/)\n- [How to identify and fix Render-Blocking Resources](https:\/\/blog.sentry.io\/how-to-id-fix-render-blocking-resources\/)\n- [Low effort image optimization tips](https:\/\/blog.sentry.io\/low-effort-image-optimization-tips\/)\n- [5 easy tips to improve your personal website performance](https:\/\/blog.sentry.io\/5-easy-tips-to-improve-your-personal-website-performance\/)\n- [How to hack your Google Lighthouse scores in 2024](https:\/\/blog.sentry.io\/how-to-hack-your-google-lighthouse-scores-in-2024\/)\n\n### More Git content\n- Resources  [What is Distributed Tracing (opens in a new tab)](https:\/\/sentry.io\/resources\/distributed-tracing-explained\/)\n- Community Series  [Identify, Trace, and Fix Endpoint Regression Issues (opens in a new tab)](https:\/\/sentry.io\/community\/series\/monitor-endpoint-regression\/)\n- ![Syntax.fm logo](https:\/\/sentry.io\/astro-assets\/legacy\/syntax-logo.png)  [Listen to the Syntax Podcast (opens in a new tab)](https:\/\/syntax.fm\/?utm_source=sentry&utm_medium=display&utm_campaign=syntax-na-podcastpromo&utm_content=logo-answers-rail-banner-listen)\n  Tasty treats for web developers brought to you by Sentry. Get tips and tricks from Wes Bos and Scott Tolinski.\n  [SEE EPISODES](https:\/\/syntax.fm\/?utm_source=sentry&utm_medium=display&utm_campaign=syntax-na-podcastpromo&utm_content=logo-answers-rail-banner-listen)\n\n## Related Answers\n[Delete a commit from a branch in Git](https:\/\/sentry.io\/answers\/delete-a-commit-from-a-branch-in-git\/)\n\nDavid Y.  —\n\nJune 15, 2023\n\n[Create a new Git branch from an existing branch](https:\/\/sentry.io\/answers\/create-a-new-git-branch-from-an-existing-branch\/)\n\nDavid Y.  —\n\nJuly 15, 2023\n\n[Revert a Git repository to a previous commit](https:\/\/sentry.io\/answers\/revert-a-git-repository-to-a-previous-commit\/)\n\nDavid Y.  —\n\nFebruary 15, 2023\n\n[Abort a merge in Git](https:\/\/sentry.io\/answers\/abort-a-merge-in-git\/)\n\nDavid Y.  —\n\nJuly 15, 2023\n\nConsidered \"not bad\" by 4 million developers and more than 150,000 organizations worldwide, Sentry provides code-level observability to many of the world's best-known companies like Disney, Peloton, Cloudflare, Eventbrite, Slack, Supercell, and Rockstar Games. Each month we process billions of exceptions from the most popular products on the internet.\n\n[learn more about sentry](https:\/\/sentry.io\/)   [join our discord](https:\/\/discord.com\/invite\/sentry)\n\n![Sentry](https:\/\/sentry.io\/_astro\/answer-cta-light.CRAdOWkA.svg)\n\n### Company\n- [About](https:\/\/sentry.io\/about\/)\n- [Blog](https:\/\/blog.sentry.io\/)\n- [Careers](https:\/\/sentry.io\/careers\/)\n- [Contact Us](https:\/\/sentry.io\/contact\/enterprise\/)\n- [Trust](https:\/\/sentry.io\/trust\/)\n\n### Platform\n- [Error Monitoring](https:\/\/sentry.io\/product\/error-monitoring\/)\n- [Tracing](https:\/\/sentry.io\/product\/tracing\/)\n- [Session Replay](https:\/\/sentry.io\/product\/session-replay\/)\n- [Seer](https:\/\/sentry.io\/product\/seer\/)\n- [Logs](https:\/\/sentry.io\/product\/logs\/)\n- [Uptime Monitoring](https:\/\/sentry.io\/product\/uptime-monitoring\/)\n- [Profiling](https:\/\/sentry.io\/product\/profiling\/)\n- [Cron Monitoring](https:\/\/sentry.io\/product\/cron-monitoring\/)\n- [Integrations](https:\/\/sentry.io\/integrations\/)\n\n### Solutions\n- [Web \/ Full Stack Development](https:\/\/sentry.io\/for\/full-stack\/)\n- [Mobile Crash Reporting](https:\/\/sentry.io\/solutions\/mobile-developers\/)\n- [Game Crash Reporting](https:\/\/sentry.io\/solutions\/game-developers\/)\n- [AI Observability](https:\/\/sentry.io\/solutions\/ai-observability\/)\n- [Application Performance Monitoring](https:\/\/sentry.io\/solutions\/application-performance-monitoring\/)\n- [Real User Monitoring](https:\/\/sentry.io\/solutions\/real-user-monitoring-rum\/)\n- [Ecommerce](https:\/\/sentry.io\/solutions\/ecommerce\/)\n- [Enterprise](https:\/\/sentry.io\/for\/enterprise\/)\n- [Startups](https:\/\/sentry.io\/for\/startups\/)\n\n### Get Help\n- [Docs](https:\/\/docs.sentry.io\/)\n- [Help Center](https:\/\/help.sentry.io\/)\n- [Status](https:\/\/status.sentry.io\/)\n- [Dev Resources](https:\/\/develop.sentry.dev\/getting-started\/)\n\n[Terms](https:\/\/sentry.io\/terms\/)  [Security & Compliance](https:\/\/sentry.io\/security\/)  [Privacy](https:\/\/sentry.io\/privacy\/)\n\n[![](https:\/\/sentry.io\/astro-assets\/nav-icons\/x-twitter.png) Twitter Menu Button](https:\/\/x.com\/sentry\/)  [![](https:\/\/sentry.io\/astro-assets\/nav-icons\/github.png) Github Social Menu Button](https:\/\/github.com\/getsentry\/)  [![](https:\/\/sentry.io\/astro-assets\/nav-icons\/linkedin.png) LinkedIn Menu Button](https:\/\/linkedin.com\/company\/getsentry\/)  [![](https:\/\/sentry.io\/astro-assets\/nav-icons\/discord.png) Discord Menu Button](https:\/\/discord.gg\/sentry)\n\n© 2026 • Sentry is a registered Trademark of Functional Software, Inc.","attrs_readable_markdown":"## The Problem\nHow do I undo the most recent local commits in Git?\n\n## The Solution\nThe [`git reset`](https:\/\/git-scm.com\/docs\/git-reset) command will return the current branch to a specified previous commit. By default, this command will remove commits from the current branch’s history while leaving the files in the working tree untouched. This allows you to redo one or more commits without losing any work.\n\nWhen calling `git reset`, you need to specify the commit to reset to. You can get the hash of the commit you want from `git log`, or you can specify an ancestor of `HEAD`, the current commit, using the [tilde (~) suffix](https:\/\/git-scm.com\/docs\/git-rev-parse#Documentation\/git-rev-parse.txt-emltrevgtltngtemegemHEADmaster3em). The following commands will undo and redo the most recent commit:\n```\ngit add .\ngit commit -m \"This commit is a mistake\"\ngit reset HEAD~\ngit add main.py # need to re-add files after reset\ngit commit -m \"This commit corrects the mistake\"\n```\nTo undo the last two commits, use the commands:\n```\ngit add .\ngit commit -m \"This commit is a mistake\"\n# make changes\ngit add .\ngit commit -m \"This commit is another mistake\"\ngit reset HEAD~2\ngit add .\ngit commit -m \"this commit corrects both mistakes\"\n```\nIf you don’t want to have to re-stage your files after a reset, you can use the `--soft` flag:\n```\ngit add .\ngit commit -m \"This commit is a mistake\"\ngit reset --soft HEAD~\n# no need to git add, as files are already staged\ngit commit -m \"This commit corrects the mistake\"\n```\nIf you want to reset both the Git history and the working tree to the state of a previous commit, you can use the `--hard` flag. Note that this will reverse all changes made to tracked files, including ones that haven’t yet been committed.\n```\ngit add .\ngit commit -m \"\"\ngit reset --hard HEAD~\n```\n`git reset --hard` should be used with caution. However, you can still retrieve any deleted commits using [`git reflog`](https:\/\/git-scm.com\/docs\/git-reflog), [up to 90 days](https:\/\/git-scm.com\/docs\/git-reflog#Documentation\/git-reflog.txt---expirelttimegt) after they were deleted. When run, `git reflog` will show a list of commits previously on the tips of branches. From this list, you can pick out the partial hash of the commit (e.g. `5c8f5a7`) to restore and create a new branch for it:\n```\ngit checkout -b restored-commit-branch 5c8f5a7\n```\nIf you would like to preserve your repository’s history but return the files to a previous state, you can use `git revert` to create new commits that do the opposite of existing commits, i.e. removing lines and files that were added and adding lines and files that were removed:\n```\ngit add .\ngit commit -m \"This commit is a mistake\"\ngit revert HEAD # will create a new commit doing the opposite of the one above\n```\nFor more on `git revert`, see our answer for [reverting to a previous commit](https:\/\/sentry.io\/answers\/revert-a-git-repository-to-a-previous-commit\/).\n\n## Further Reading\nIf you’re looking to get a deeper understanding of how web performance optimization works, take a look at the following articles:\n\n- [From LCP to CLS: Improve your Core Web Vitals with Image Loading Best Practices](https:\/\/blog.sentry.io\/from-lcp-to-cls-improve-your-core-web-vitals-with-image-loading-best\/)\n- [How to identify and fix Render-Blocking Resources](https:\/\/blog.sentry.io\/how-to-id-fix-render-blocking-resources\/)\n- [Low effort image optimization tips](https:\/\/blog.sentry.io\/low-effort-image-optimization-tips\/)\n- [5 easy tips to improve your personal website performance](https:\/\/blog.sentry.io\/5-easy-tips-to-improve-your-personal-website-performance\/)\n- [How to hack your Google Lighthouse scores in 2024](https:\/\/blog.sentry.io\/how-to-hack-your-google-lighthouse-scores-in-2024\/)","meta_canonical":null}

3. Robots.txt Check

Query:

Response:

4. Spam/Ban Check

Query:

Response:

5. Seen Status Check

ℹ️ Skipped - page is already crawled

📄

INDEXABLE

✅

CRAWLED

6 hours ago

🤖

ROBOTS ALLOWED

Page Info Filters

Filter	Status	Condition	Details
HTTP status	PASS	`download_http_code = 200`	HTTP 200
Age cutoff	PASS	`download_stamp > now() - 6 MONTH`	0 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

Page Details

Property	Value
URL	https://sentry.io/answers/undo-the-most-recent-local-git-commits/
Last Crawled	2026-04-08 03:30:24 (6 hours ago)
First Indexed	2023-06-21 06:47:38 (2 years ago)
HTTP Status Code	200
Meta Title	Undo the most recent local Git commits \| Sentry
Meta Description	Sentry helps developers monitor and fix crashes in real time. Get the details you need to resolve the most important issues quickly.
Meta Canonical	null
Boilerpipe Text	The Problem How do I undo the most recent local commits in Git? The Solution The git reset command will return the current branch to a specified previous commit. By default, this command will remove commits from the current branch’s history while leaving the files in the working tree untouched. This allows you to redo one or more commits without losing any work. When calling git reset , you need to specify the commit to reset to. You can get the hash of the commit you want from git log , or you can specify an ancestor of HEAD , the current commit, using the tilde (~) suffix . The following commands will undo and redo the most recent commit: git add . git commit -m "This commit is a mistake" git reset HEAD~ git add main.py # need to re-add files after reset git commit -m "This commit corrects the mistake" To undo the last two commits, use the commands: git add . git commit -m "This commit is a mistake" # make changes git add . git commit -m "This commit is another mistake" git reset HEAD~2 git add . git commit -m "this commit corrects both mistakes" If you don’t want to have to re-stage your files after a reset, you can use the --soft flag: git add . git commit -m "This commit is a mistake" git reset --soft HEAD~ # no need to git add, as files are already staged git commit -m "This commit corrects the mistake" If you want to reset both the Git history and the working tree to the state of a previous commit, you can use the --hard flag. Note that this will reverse all changes made to tracked files, including ones that haven’t yet been committed. git add . git commit -m "" git reset --hard HEAD~ git reset --hard should be used with caution. However, you can still retrieve any deleted commits using git reflog , up to 90 days after they were deleted. When run, git reflog will show a list of commits previously on the tips of branches. From this list, you can pick out the partial hash of the commit (e.g. 5c8f5a7 ) to restore and create a new branch for it: git checkout -b restored-commit-branch 5c8f5a7 If you would like to preserve your repository’s history but return the files to a previous state, you can use git revert to create new commits that do the opposite of existing commits, i.e. removing lines and files that were added and adding lines and files that were removed: git add . git commit -m "This commit is a mistake" git revert HEAD # will create a new commit doing the opposite of the one above For more on git revert , see our answer for reverting to a previous commit . Further Reading If you’re looking to get a deeper understanding of how web performance optimization works, take a look at the following articles: From LCP to CLS: Improve your Core Web Vitals with Image Loading Best Practices How to identify and fix Render-Blocking Resources Low effort image optimization tips 5 easy tips to improve your personal website performance How to hack your Google Lighthouse scores in 2024
Markdown	[Skip to main content](https://sentry.io/answers/undo-the-most-recent-local-git-commits/#main-content) Menu Platform Products - [Error Monitoring](https://sentry.io/product/error-monitoring/) - [Logs](https://sentry.io/product/logs/) - [Session Replay](https://sentry.io/product/session-replay/) - [Tracing](https://sentry.io/product/tracing/) - [Seer NEW](https://sentry.io/product/seer/) - [Profiling](https://sentry.io/product/profiling/) - [AI Code Review NEW](https://sentry.io/product/seer/ai-code-review/) - [Size Analysis NEW](https://sentry.io/product/size-analysis) - [Cron Monitoring](https://sentry.io/product/cron-monitoring/) - [Uptime Monitoring](https://sentry.io/product/uptime-monitoring/) - [Sentry CLI NEW](https://cli.sentry.dev/) Integrations - [![](https://sentry.io/astro-assets/nav-icons/github.png)Github](https://sentry.io/integrations/github/) - [![](https://sentry.io/astro-assets/nav-icons/slack.png)Slack](https://sentry.io/integrations/slack/) - [Sentry MCP NEW](https://mcp.sentry.dev/) - [All Integrations](https://sentry.io/integrations/) SDKs - [![](https://sentry.io/astro-assets/nav-icons/javascript.png)Javascript](https://sentry.io/for/javascript/) - [![](https://sentry.io/astro-assets/nav-icons/python.png)Python](https://sentry.io/for/python/) - [![](https://sentry.io/astro-assets/nav-icons/react.png)React](https://sentry.io/for/react/) - [![](https://sentry.io/astro-assets/nav-icons/laravel.png)Laravel](https://sentry.io/for/laravel/) - [![](https://sentry.io/astro-assets/nav-icons/nextjs.png)Next.js](https://sentry.io/for/nextjs/) - [All SDKs](https://sentry.io/platforms/) Solutions ### Solutions - [Web / Full Stack Development](https://sentry.io/for/full-stack/) - [Mobile Crash Reporting](https://sentry.io/solutions/mobile-developers/) - [Game Crash Reporting](https://sentry.io/solutions/game-developers/) - [AI Observability](https://sentry.io/solutions/ai-observability/) - [Application Performance Monitoring](https://sentry.io/solutions/application-performance-monitoring/) - [Real User Monitoring](https://sentry.io/solutions/real-user-monitoring-rum/) - [Ecommerce](https://sentry.io/solutions/ecommerce/) - [Enterprise](https://sentry.io/for/enterprise/) - [Startups](https://sentry.io/for/startups/) Resources Learn - [Blog](https://blog.sentry.io/) - [Changelog](https://sentry.io/changelog/) - [Sandbox](https://sandbox.sentry.io/) - [Resources](https://sentry.io/resources/) - [Syntax](https://syntax.fm/) - [Customers](https://sentry.io/customers/) - [Cookbook](https://sentry.io/cookbook/) Support - [Contact Us](https://sentry.io/contact/enterprise/) - [Help Center](https://help.sentry.io/) - [Status](https://status.sentry.io/) Hang out with us - [Sentry Build](https://sentry.io/resources/sentry-build/) - [Events](https://sentry.io/events/) - [Merch](https://sentry.shop/) [Docs](https://docs.sentry.io/) [Pricing](https://sentry.io/pricing/) [Sign In](https://sentry.io/auth/login/) [Get Demo](https://sentry.io/demo/) [Get Started](https://sentry.io/signup/) - Platform - Solutions - [Web / Full Stack Development](https://sentry.io/for/full-stack/) - [Mobile Crash Reporting](https://sentry.io/solutions/mobile-developers/) - [Game Crash Reporting](https://sentry.io/solutions/game-developers/) - [AI Observability](https://sentry.io/solutions/ai-observability/) - [Application Performance Monitoring](https://sentry.io/solutions/application-performance-monitoring/) - [Real User Monitoring](https://sentry.io/solutions/real-user-monitoring-rum/) - [Ecommerce](https://sentry.io/solutions/ecommerce/) - [Enterprise](https://sentry.io/for/enterprise/) - [Startups](https://sentry.io/for/startups/) - Resources - [Docs](https://docs.sentry.io/) - [Pricing](https://sentry.io/pricing/) [Sign In](https://sentry.io/auth/login/) [Get Demo](https://sentry.io/demo/) [Get Started](https://sentry.io/signup/) [Sentry Answers](https://sentry.io/answers/) \> [Git](https://sentry.io/answers/git/) \> Undo the most recent local Git commits # Undo the most recent local Git commits ![](https://sentry.io/astro-assets/legacy/ghost.png) David Y. — February 15, 2023 [jump to solution](https://sentry.io/answers/undo-the-most-recent-local-git-commits/#the-solution) ## The Problem How do I undo the most recent local commits in Git? ## The Solution The [`git reset`](https://git-scm.com/docs/git-reset) command will return the current branch to a specified previous commit. By default, this command will remove commits from the current branch’s history while leaving the files in the working tree untouched. This allows you to redo one or more commits without losing any work. When calling `git reset`, you need to specify the commit to reset to. You can get the hash of the commit you want from `git log`, or you can specify an ancestor of `HEAD`, the current commit, using the [tilde (~) suffix](https://git-scm.com/docs/git-rev-parse#Documentation/git-rev-parse.txt-emltrevgtltngtemegemHEADmaster3em). The following commands will undo and redo the most recent commit: ``` git add . git commit -m "This commit is a mistake" git reset HEAD~ git add main.py # need to re-add files after reset git commit -m "This commit corrects the mistake" ``` To undo the last two commits, use the commands: ``` git add . git commit -m "This commit is a mistake" # make changes git add . git commit -m "This commit is another mistake" git reset HEAD~2 git add . git commit -m "this commit corrects both mistakes" ``` If you don’t want to have to re-stage your files after a reset, you can use the `--soft` flag: ``` git add . git commit -m "This commit is a mistake" git reset --soft HEAD~ # no need to git add, as files are already staged git commit -m "This commit corrects the mistake" ``` If you want to reset both the Git history and the working tree to the state of a previous commit, you can use the `--hard` flag. Note that this will reverse all changes made to tracked files, including ones that haven’t yet been committed. ``` git add . git commit -m "" git reset --hard HEAD~ ``` `git reset --hard` should be used with caution. However, you can still retrieve any deleted commits using [`git reflog`](https://git-scm.com/docs/git-reflog), [up to 90 days](https://git-scm.com/docs/git-reflog#Documentation/git-reflog.txt---expirelttimegt) after they were deleted. When run, `git reflog` will show a list of commits previously on the tips of branches. From this list, you can pick out the partial hash of the commit (e.g. `5c8f5a7`) to restore and create a new branch for it: ``` git checkout -b restored-commit-branch 5c8f5a7 ``` If you would like to preserve your repository’s history but return the files to a previous state, you can use `git revert` to create new commits that do the opposite of existing commits, i.e. removing lines and files that were added and adding lines and files that were removed: ``` git add . git commit -m "This commit is a mistake" git revert HEAD # will create a new commit doing the opposite of the one above ``` For more on `git revert`, see our answer for [reverting to a previous commit](https://sentry.io/answers/revert-a-git-repository-to-a-previous-commit/). ## Further Reading If you’re looking to get a deeper understanding of how web performance optimization works, take a look at the following articles: - [From LCP to CLS: Improve your Core Web Vitals with Image Loading Best Practices](https://blog.sentry.io/from-lcp-to-cls-improve-your-core-web-vitals-with-image-loading-best/) - [How to identify and fix Render-Blocking Resources](https://blog.sentry.io/how-to-id-fix-render-blocking-resources/) - [Low effort image optimization tips](https://blog.sentry.io/low-effort-image-optimization-tips/) - [5 easy tips to improve your personal website performance](https://blog.sentry.io/5-easy-tips-to-improve-your-personal-website-performance/) - [How to hack your Google Lighthouse scores in 2024](https://blog.sentry.io/how-to-hack-your-google-lighthouse-scores-in-2024/) ### More Git content - Resources [What is Distributed Tracing (opens in a new tab)](https://sentry.io/resources/distributed-tracing-explained/) - Community Series [Identify, Trace, and Fix Endpoint Regression Issues (opens in a new tab)](https://sentry.io/community/series/monitor-endpoint-regression/) - ![Syntax.fm logo](https://sentry.io/astro-assets/legacy/syntax-logo.png) [Listen to the Syntax Podcast (opens in a new tab)](https://syntax.fm/?utm_source=sentry&utm_medium=display&utm_campaign=syntax-na-podcastpromo&utm_content=logo-answers-rail-banner-listen) Tasty treats for web developers brought to you by Sentry. Get tips and tricks from Wes Bos and Scott Tolinski. [SEE EPISODES](https://syntax.fm/?utm_source=sentry&utm_medium=display&utm_campaign=syntax-na-podcastpromo&utm_content=logo-answers-rail-banner-listen) ## Related Answers [Delete a commit from a branch in Git](https://sentry.io/answers/delete-a-commit-from-a-branch-in-git/) David Y. — June 15, 2023 [Create a new Git branch from an existing branch](https://sentry.io/answers/create-a-new-git-branch-from-an-existing-branch/) David Y. — July 15, 2023 [Revert a Git repository to a previous commit](https://sentry.io/answers/revert-a-git-repository-to-a-previous-commit/) David Y. — February 15, 2023 [Abort a merge in Git](https://sentry.io/answers/abort-a-merge-in-git/) David Y. — July 15, 2023 Considered "not bad" by 4 million developers and more than 150,000 organizations worldwide, Sentry provides code-level observability to many of the world's best-known companies like Disney, Peloton, Cloudflare, Eventbrite, Slack, Supercell, and Rockstar Games. Each month we process billions of exceptions from the most popular products on the internet. [learn more about sentry](https://sentry.io/) [join our discord](https://discord.com/invite/sentry) ![Sentry](https://sentry.io/_astro/answer-cta-light.CRAdOWkA.svg) ### Company - [About](https://sentry.io/about/) - [Blog](https://blog.sentry.io/) - [Careers](https://sentry.io/careers/) - [Contact Us](https://sentry.io/contact/enterprise/) - [Trust](https://sentry.io/trust/) ### Platform - [Error Monitoring](https://sentry.io/product/error-monitoring/) - [Tracing](https://sentry.io/product/tracing/) - [Session Replay](https://sentry.io/product/session-replay/) - [Seer](https://sentry.io/product/seer/) - [Logs](https://sentry.io/product/logs/) - [Uptime Monitoring](https://sentry.io/product/uptime-monitoring/) - [Profiling](https://sentry.io/product/profiling/) - [Cron Monitoring](https://sentry.io/product/cron-monitoring/) - [Integrations](https://sentry.io/integrations/) ### Solutions - [Web / Full Stack Development](https://sentry.io/for/full-stack/) - [Mobile Crash Reporting](https://sentry.io/solutions/mobile-developers/) - [Game Crash Reporting](https://sentry.io/solutions/game-developers/) - [AI Observability](https://sentry.io/solutions/ai-observability/) - [Application Performance Monitoring](https://sentry.io/solutions/application-performance-monitoring/) - [Real User Monitoring](https://sentry.io/solutions/real-user-monitoring-rum/) - [Ecommerce](https://sentry.io/solutions/ecommerce/) - [Enterprise](https://sentry.io/for/enterprise/) - [Startups](https://sentry.io/for/startups/) ### Get Help - [Docs](https://docs.sentry.io/) - [Help Center](https://help.sentry.io/) - [Status](https://status.sentry.io/) - [Dev Resources](https://develop.sentry.dev/getting-started/) [Terms](https://sentry.io/terms/) [Security & Compliance](https://sentry.io/security/) [Privacy](https://sentry.io/privacy/) [![](https://sentry.io/astro-assets/nav-icons/x-twitter.png) Twitter Menu Button](https://x.com/sentry/) [![](https://sentry.io/astro-assets/nav-icons/github.png) Github Social Menu Button](https://github.com/getsentry/) [![](https://sentry.io/astro-assets/nav-icons/linkedin.png) LinkedIn Menu Button](https://linkedin.com/company/getsentry/) [![](https://sentry.io/astro-assets/nav-icons/discord.png) Discord Menu Button](https://discord.gg/sentry) © 2026 • Sentry is a registered Trademark of Functional Software, Inc.
Readable Markdown	## The Problem How do I undo the most recent local commits in Git? ## The Solution The [`git reset`](https://git-scm.com/docs/git-reset) command will return the current branch to a specified previous commit. By default, this command will remove commits from the current branch’s history while leaving the files in the working tree untouched. This allows you to redo one or more commits without losing any work. When calling `git reset`, you need to specify the commit to reset to. You can get the hash of the commit you want from `git log`, or you can specify an ancestor of `HEAD`, the current commit, using the [tilde (~) suffix](https://git-scm.com/docs/git-rev-parse#Documentation/git-rev-parse.txt-emltrevgtltngtemegemHEADmaster3em). The following commands will undo and redo the most recent commit: ``` git add . git commit -m "This commit is a mistake" git reset HEAD~ git add main.py # need to re-add files after reset git commit -m "This commit corrects the mistake" ``` To undo the last two commits, use the commands: ``` git add . git commit -m "This commit is a mistake" # make changes git add . git commit -m "This commit is another mistake" git reset HEAD~2 git add . git commit -m "this commit corrects both mistakes" ``` If you don’t want to have to re-stage your files after a reset, you can use the `--soft` flag: ``` git add . git commit -m "This commit is a mistake" git reset --soft HEAD~ # no need to git add, as files are already staged git commit -m "This commit corrects the mistake" ``` If you want to reset both the Git history and the working tree to the state of a previous commit, you can use the `--hard` flag. Note that this will reverse all changes made to tracked files, including ones that haven’t yet been committed. ``` git add . git commit -m "" git reset --hard HEAD~ ``` `git reset --hard` should be used with caution. However, you can still retrieve any deleted commits using [`git reflog`](https://git-scm.com/docs/git-reflog), [up to 90 days](https://git-scm.com/docs/git-reflog#Documentation/git-reflog.txt---expirelttimegt) after they were deleted. When run, `git reflog` will show a list of commits previously on the tips of branches. From this list, you can pick out the partial hash of the commit (e.g. `5c8f5a7`) to restore and create a new branch for it: ``` git checkout -b restored-commit-branch 5c8f5a7 ``` If you would like to preserve your repository’s history but return the files to a previous state, you can use `git revert` to create new commits that do the opposite of existing commits, i.e. removing lines and files that were added and adding lines and files that were removed: ``` git add . git commit -m "This commit is a mistake" git revert HEAD # will create a new commit doing the opposite of the one above ``` For more on `git revert`, see our answer for [reverting to a previous commit](https://sentry.io/answers/revert-a-git-repository-to-a-previous-commit/). ## Further Reading If you’re looking to get a deeper understanding of how web performance optimization works, take a look at the following articles: - [From LCP to CLS: Improve your Core Web Vitals with Image Loading Best Practices](https://blog.sentry.io/from-lcp-to-cls-improve-your-core-web-vitals-with-image-loading-best/) - [How to identify and fix Render-Blocking Resources](https://blog.sentry.io/how-to-id-fix-render-blocking-resources/) - [Low effort image optimization tips](https://blog.sentry.io/low-effort-image-optimization-tips/) - [5 easy tips to improve your personal website performance](https://blog.sentry.io/5-easy-tips-to-improve-your-personal-website-performance/) - [How to hack your Google Lighthouse scores in 2024](https://blog.sentry.io/how-to-hack-your-google-lighthouse-scores-in-2024/)
Shard	147 (laksa)
Root Hash	17800916657557307547
Unparsed URL	io,sentry!/answers/undo-the-most-recent-local-git-commits/ s443