🕷️ Crawler Inspector

URL Lookup

Direct Parameter Lookup

Raw Queries and Responses

1. Shard Calculation

Query:

Response:

Calculated Shard: 95 (from laksa198)

2. Crawled Status Check

Query:

curl -X POST \
  'http://laksa095.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://www.linode.com/docs/guides/revert-last-git-commit/\')), getAhrefsUnparsedNoserviceFromURL(\'https://www.linode.com/docs/guides/revert-last-git-commit/\'))) FORMAT JSONEachRow'

Response:

{"found_url":"https:\/\/www.linode.com\/docs\/guides\/revert-last-git-commit\/","crawl_time":1772744266,"first_indexed_time":1667018997,"http_code":200,"src_unparsed":"com,linode!www,\/docs\/guides\/revert-last-git-commit\/ s443","src_root_hash":"1749289081436496295","history_drop_reason":null,"meta_title":"How to Revert the Last Commit in Git | Linode Docs","meta_descriptions":["Mistakes happen, and the Git version control system has tools to help you navigate them. In this tutorial, learn two methods to undo your most recent Git commit, what sets the methods apart, and when to use them."],"attrs_boilerpipe_text":"Git is a widely used Version Control System (VCS) known for its versatility. It utilizes local clones of central repositories and keeps track of every commit so changes can be rolled back as needed.\nYou might need that recoverability after an inadvertent commit or to undo a commit for any reason. This tutorial shows you how to use the\ngit\ncommand line utility to revert a commit. It covers methods using both the\ngit revert\nand\ngit reset\ncommands and explains the differences.\nLearn more about Git generally in our guide\nGit vs SVN: Pros and Cons of Each Version Control System\n. For a more general, and thorough, coverage of reverting Git commits, take a look at our guide on\nHow to Undo a Git Commit\n.\nOptional: Create a Test Repository\nIf you’d like to test reverting and resetting in a separate repository from one you actively work in, follow the steps below. This will set up an example Git repository similar to the one used for the examples in this tutorial. The commit IDs may be different, but the contents of the repository should otherwise be the same.\nThe steps presume you have already installed Git and done basic configuration (e.g. user email address and name). If you have not done this yet, you can learn how in our guide\nHow to Install Git and Clone a GitHub Repository\n.\nCreate a new directory for your Git repository, and change it into that directory. Here, the new directory,\ngit-example\nis created in the current user’s home directory.\nmkdir ~\/git-example\ncd\n~\/git-example\nFrom here on, you should execute the given commands while working in this directory.\nInitialize the new Git repository.\ngit init\nUse the\ntouch\ncommand to create some new empty files.\ntouch example-file-1.txt\ntouch example-file-2.txt\nAdd the files to the Git staging area, then commit the staged changes.\ngit add .\ngit commit -m\n\"Initialized repo.\"\nMake some changes to the first file, adding some content to it. Then stage and commit those changes using the following commands:\nDo the same for the second file.\nYou now have a Git repository with a couple of files and several commits, which you can see listed with the following command:\ngit log --oneline\nThe output of the command looks like the following:\nf4391b2 (HEAD -> master) Added text to second file.\ne3c534a Added text to first file.\n0b24777 Initialized repo.\nHow to Use the\ngit revert\nCommand on the Last Commit\nGit revert undoes a commit by comparing the changes made in that commit to the repository’s previous state. It then creates a new commit that reverts the changes.\nTo use the\ngit revert\ncommand, you first need the ID for that commit. You can get this with the\ngit log\ncommand. Here, the command is used with the\n--oneline\noption to make each commit display on a single line:\ngit log --oneline\nf4391b2 (HEAD -> master) Added text to second file.\ne3c534a Added text to first file.\n0b24777 Initialized repo.\nThe line at the top of the output, with an ID of\nf4391b2\nin this example, represents the last commit. You can revert that commit using the\nrevert\ncommand with that commit’s ID, as shown here:\ngit revert f4391b2\nGit starts a new commit to revert the changes. It may present you with a text editor allowing you to edit the description for the new commit. When you are satisfied with the description, exit the text editor to complete the reversion.\n[master e86542a] Revert \"Added text to second file.\"\n 1 file changed, 1 deletion(-)\nRunning the\ngit log\ncommand again shows that there is now a new commit to revert the previous commit:\ngit log --oneline\ne86542a (HEAD -> master) Revert \"Added text to second file.\"\nf4391b2 Added text to second file.\ne3c534a Added text to first file.\n0b24777 Initialized repo.\nIf you view the affected file, you can see that the changes have been reversed. In this case, that is\nexample-file-2.txt\n:\ncat example-file-2.txt\nHow to Use the\ngit reset\nCommand to Undo Commits\nGit reset can also be used to revert the last commit. The command is more powerful than\ngit revert\nand works by removing commits entirely from the repository’s commit history. Essentially, reset “rewinds” you to a previous commit, eliminating later commits and history along the way.\nWith the\ngit reset\ncommand, you have access to the\nHEAD~1\nalias. This alias stands in for the ID of the previous commit, providing easy access when trying to revert to the last commit.\nThe\ngit reset\ncommand comes with three flags that define how the command deals with changed files in the working directory and staging area.\nUse the\n--soft\noption to roll back to a previous commit, while preserving file changes in the working directory and staging area.\ngit reset --soft HEAD~1\nUse the\n--hard\noption to likewise roll back to a previous commit. However, this option results in all file changes being reverted as well. Changes to files in the working directory as well as staged changes are both discarded.\ngit reset --hard HEAD~1\nUse the\n--mixed\noption to, again, roll back to a previous commit. Here, a middle ground is adopted for file changes. As with the\n--hard\noption, changes made to files in the working directory are discarded. However, like the\n--soft\noption, staged changes are preserved.\ngit reset --mixed HEAD~1\nAfter any of the above commands, you can see that the last commit has been removed from the Git commit history:\ngit log --oneline\ne3c534a (HEAD -> master) Added text to first file.\n0b24777 Initialized repo.\nDifferences Between Reset and Revert\nThe main difference between the\ngit reset\nand\ngit revert\ncommands is the commit history.\nRevert aims to maintain a full commit history, undoing a commit by assessing changes and making a new commit that reverses them. This actually means that this command adds to the commit history. It gives you full transparency to past commits and their reversions.\nIn contrast, using reset discards commits even from the commit history, making them impossible to recover later. The\ngit reset\ncommand can even do the same for local file changes. This option keeps you from seeing reversions and the original commits that are reverted.\nGenerally, it is recommended that you use\ngit revert\nfor backing out a commit. It keeps a record of the removed commit and leaves the possibility of assessing and accessing the commit history later.\nThe\ngit reset\ncommand should be used sparingly. Take a good look at the situation to ensure that it cannot be remedied by reverting a commit instead of resetting to a previous commit. A reset might be preferred, however, for immediately undoing mistaken commits, when there is less chance that you need options for recovering the changes.\nConclusion\nThat covers all you need to revert recent Git commits. Moreover, the techniques covered in this tutorial can also help you manage Git commits more generally. The\ngit revert\ncommand can be useful for precisely removing past commits while retaining your commit history. The\ngit reset\ncommand, on the other hand, provides a more radical option, completely reverting a repository to a previous commit, including the commit history.\nTo keep learning, refer to the links at the beginning of this guide. These give you more on Git generally as well as more on the commands covered in this tutorial. You may also want to look at our entire lineup of\nguides on version control\n. These cover everything from the fundamentals to particular use cases, and provide steps to deepen your version control knowledge.\nMore Information\nYou may wish to consult the following resources for additional information\non this topic. While these are provided in the hope that they will be\nuseful, please note that we cannot vouch for the accuracy or timeliness of\nexternally hosted materials.\nfreeCodeCamp: Git Revert Commit – How to Undo the Last Commit\nTechTarget: How to Revert a Git Commit\nThis page was originally published on\nAugust 18, 2022.","attrs_markdown":"- [Search](https:\/\/www.linode.com\/search\/)\n- [Docs](https:\/\/techdocs.akamai.com\/cloud-computing\/docs\/welcome)\n- [Blog](https:\/\/www.linode.com\/blog\/)\n- [Support](https:\/\/www.linode.com\/support\/)\n- [Sales](https:\/\/www.linode.com\/company\/contact\/)\n- [Log in](https:\/\/login.linode.com\/login)\n\n[![Akamai Cloud](https:\/\/www.linode.com\/linode\/en\/images\/logo\/akamai-cloud-logo.svg)](https:\/\/www.linode.com\/)\n\n- Explore\n- Products\n- Solutions\n- Pricing\n- Resources\n- [Partners](https:\/\/www.linode.com\/partners\/)\n- [Sign up](https:\/\/login.linode.com\/signup)\n- Mobile\n\n- Explore\n  - [Lower costs](https:\/\/www.linode.com\/reduce-cloud-costs\/)\n  - [Lower latency](https:\/\/www.linode.com\/low-latency-applications\/)\n  - [Cloud portability](https:\/\/www.linode.com\/cloud-portability\/)\n  - [Global scale](https:\/\/www.linode.com\/cloud-global-scale\/)\n  - [Our platform](https:\/\/www.linode.com\/global-infrastructure\/)\n  - [Support experience](https:\/\/www.linode.com\/support-experience\/)\n- Products\n  - [Products Overview](https:\/\/www.linode.com\/products\/)\n  - Compute\n    - [Essential Compute](https:\/\/www.linode.com\/products\/essential-compute\/)\n    - [GPU](https:\/\/www.linode.com\/products\/gpu\/)\n    - [Accelerated Compute](https:\/\/www.linode.com\/products\/accelerated-compute\/)\n    - [Kubernetes](https:\/\/www.linode.com\/products\/kubernetes\/)\n    - [App Platform](https:\/\/www.linode.com\/products\/app-platform\/)\n  - Storage\n    - [Block Storage](https:\/\/www.linode.com\/products\/block-storage\/)\n    - [Object Storage](https:\/\/www.linode.com\/products\/object-storage\/)\n    - [Backups](https:\/\/www.linode.com\/products\/backups\/)\n  - Networking\n    - [Cloud Firewall](https:\/\/www.linode.com\/products\/cloud-firewall\/)\n    - [DNS Manager](https:\/\/www.linode.com\/products\/dns-manager\/)\n    - [NodeBalancers](https:\/\/www.linode.com\/products\/nodebalancers\/)\n    - [Private Networking](https:\/\/www.linode.com\/products\/private-networking\/)\n  - Databases\n    - [Managed Databases](https:\/\/www.linode.com\/products\/databases\/)\n  - Services\n    - [Linode Managed](https:\/\/www.linode.com\/products\/managed\/)\n- Solutions\n  - [AI inferencing](https:\/\/www.linode.com\/solutions\/ai-inferencing\/)\n  - [Ecommerce](https:\/\/www.linode.com\/solutions\/ecommerce\/)\n  - [Gaming](https:\/\/www.linode.com\/solutions\/gaming\/)\n  - [Managed hosting](https:\/\/www.linode.com\/solutions\/managed-hosting\/)\n  - [Media](https:\/\/www.linode.com\/solutions\/media\/)\n  - [SaaS](https:\/\/www.linode.com\/solutions\/saas\/)\n- Pricing\n  - [Pricing list](https:\/\/www.linode.com\/pricing\/)\n  - [Cloud computing calculator](https:\/\/www.linode.com\/pricing\/cloud-cost-calculator\/)\n- Resources\n  - [White paper, ebooks, videos…](https:\/\/www.linode.com\/resources\/)\n  - [Developer hub](https:\/\/www.linode.com\/developers\/)\n  - [Documentation](https:\/\/techdocs.akamai.com\/cloud-computing\/docs\/welcome)\n  - [Guides](https:\/\/www.linode.com\/docs\/)\n  - [Reference architectures](https:\/\/www.linode.com\/docs\/reference-architecture\/)\n  - [Community Q\\&A](https:\/\/www.linode.com\/community\/questions\/)\n  - [Beta program](https:\/\/www.linode.com\/green-light\/)\n  - [Startup program](https:\/\/www.linode.com\/startup-programs\/)\n  - [Marketplace apps](https:\/\/www.linode.com\/marketplace\/)\n  - [Blog](https:\/\/www.linode.com\/blog\/)\n  - [Events and workshops](https:\/\/www.linode.com\/events\/)\n- [Partners](https:\/\/www.linode.com\/partners\/)\n- Company\n  - [About Us](https:\/\/www.linode.com\/company\/about\/)\n  - [Newsroom](https:\/\/www.akamai.com\/newsroom)\n  - [Careers](https:\/\/www.akamai.com\/careers)\n  - [Legal](https:\/\/www.linode.com\/legal\/)\n  - [Sales](https:\/\/www.linode.com\/company\/contact\/)\n  - [System Status](https:\/\/status.linode.com\/)\n\n- Search\n- [Docs](https:\/\/techdocs.akamai.com\/cloud-computing\/docs\/welcome)\n- [Blog](https:\/\/www.linode.com\/blog\/)\n- [Resources](https:\/\/www.linode.com\/resources\/)\n- [Pricing](https:\/\/www.linode.com\/pricing\/)\n- [Support](https:\/\/www.linode.com\/support\/)\n- [Sales](https:\/\/www.linode.com\/company\/contact\/)\n\n- [Log in](https:\/\/login.linode.com\/login)\n- [Sign up](https:\/\/login.linode.com\/signup)\n\n###### Featured\n[![Hero Forge Craft of Code Header](https:\/\/www.linode.com\/ns\/features\/prod\/images\/hero-forge-craft-of-code-632x279.jpg)Hero Forge Secure, accessible GPU instances. Unleash millions of adventures. Read story](https:\/\/www.akamai.com\/resources\/customer-story\/hero-forge)\n\n- [Lower costs](https:\/\/www.linode.com\/reduce-cloud-costs\/)\n- [Lower latency](https:\/\/www.linode.com\/low-latency-applications\/)\n- [Cloud portability](https:\/\/www.linode.com\/cloud-portability\/)\n- [Global scale](https:\/\/www.linode.com\/cloud-global-scale\/)\n\n- [Our platform](https:\/\/www.linode.com\/global-infrastructure\/)\n- [Support experience](https:\/\/www.linode.com\/support-experience\/)\n\n###### Featured\n[![GPU acceleration](https:\/\/www.linode.com\/ns\/features\/prod\/images\/gpu-438.png)GPU acceleration Power AI and media workloads with on-demand NVIDIA™ GPUs at cost-effective pricing. View product details](https:\/\/www.linode.com\/products\/gpu\/)\n\n[View all products](https:\/\/www.linode.com\/products\/)\n\n###### Compute\n- [Essential Compute](https:\/\/www.linode.com\/products\/essential-compute\/)\n- [GPU](https:\/\/www.linode.com\/products\/gpu\/)\n- [Accelerated Compute](https:\/\/www.linode.com\/products\/accelerated-compute\/)\n- [Kubernetes](https:\/\/www.linode.com\/products\/kubernetes\/)\n- [App Platform](https:\/\/www.linode.com\/products\/app-platform\/)\n\n###### Storage\n- [Block Storage](https:\/\/www.linode.com\/products\/block-storage\/)\n- [Object Storage](https:\/\/www.linode.com\/products\/object-storage\/)\n- [Backups](https:\/\/www.linode.com\/products\/backups\/)\n\n###### Networking\n- [Cloud Firewall](https:\/\/www.linode.com\/products\/cloud-firewall\/)\n- [DNS Manager](https:\/\/www.linode.com\/products\/dns-manager\/)\n- [NodeBalancers](https:\/\/www.linode.com\/products\/nodebalancers\/)\n- [Private Networking](https:\/\/www.linode.com\/products\/private-networking\/)\n\n###### Databases\n- [Managed Databases](https:\/\/www.linode.com\/products\/databases\/)\n\n###### Services\n- [Linode Managed](https:\/\/www.linode.com\/products\/managed\/)\n\n###### Featured\n[![Portability in the Cloud: Best Practices for Building SaaS-Based Applications](https:\/\/www.linode.com\/ns\/features\/prod\/images\/MRK-4404-Portability-i632x217-px.jpg)Portability in the cloud Best practices for building SaaS-based applications. Get your copy](https:\/\/www.linode.com\/resources\/ebook\/cloud-portability-saas-applications\/)\n\n###### Solutions\n- [AI inferencing](https:\/\/www.linode.com\/solutions\/ai-inferencing\/)\n- [Ecommerce](https:\/\/www.linode.com\/solutions\/ecommerce\/)\n- [Gaming](https:\/\/www.linode.com\/solutions\/gaming\/)\n- [Managed hosting](https:\/\/www.linode.com\/solutions\/managed-hosting\/)\n- [Media](https:\/\/www.linode.com\/solutions\/media\/)\n- [SaaS](https:\/\/www.linode.com\/solutions\/saas\/)\n\n###### Featured\n[![Cloud Pricing Calculator](https:\/\/www.linode.com\/ns\/features\/prod\/images\/Cloud_Pricing_MockUp2-416x376.png)Cloud computing calculator Estimate your cloud costs. Price and configure cloud features to match your needs. Launch calculator](https:\/\/www.linode.com\/pricing\/cloud-cost-calculator\/)\n\n###### Pricing\n- [Pricing list](https:\/\/www.linode.com\/pricing\/)\n- [Cloud computing calculator](https:\/\/www.linode.com\/pricing\/cloud-cost-calculator\/)\n\n###### Featured\n[![](https:\/\/www.linode.com\/ns\/features\/prod\/images\/developerHub-submenu-sm.jpg)Developer hub Comprehensive guides, documentation, and endpoints. Everything you need to get started. Visit hub](https:\/\/www.linode.com\/developers\/)\n\n###### Library\n- [White paper, ebooks, videos…](https:\/\/www.linode.com\/resources\/)\n\n###### Technical Resources\n- [Developer hub](https:\/\/www.linode.com\/developers\/)\n- [Documentation](https:\/\/techdocs.akamai.com\/cloud-computing\/docs\/welcome)\n- [Guides](https:\/\/www.linode.com\/docs\/)\n- [Reference architectures](https:\/\/www.linode.com\/docs\/reference-architecture\/)\n\n###### Community\n- [Community Q\\&A](https:\/\/www.linode.com\/community\/questions\/)\n- [Beta program](https:\/\/www.linode.com\/green-light\/)\n- [Startup program](https:\/\/www.linode.com\/startup-programs\/)\n\n###### Marketplace\n- [Browse apps](https:\/\/www.linode.com\/marketplace\/)\n\n###### What's New\n- [Blog](https:\/\/www.linode.com\/blog\/)\n- [Events and workshops](https:\/\/www.linode.com\/events\/)\n\nExplore docs\n\n1. [Docs Home](https:\/\/www.linode.com\/docs\/)\n2. [Guides](https:\/\/www.linode.com\/docs\/guides\/)\n3. [Development](https:\/\/www.linode.com\/docs\/guides\/development\/)\n4. [Version Control](https:\/\/www.linode.com\/docs\/guides\/development\/version-control\/)\n\n- On this page\n  \n  On this page\n\n### On this page\n1. [Optional: Create a Test Repository](https:\/\/www.linode.com\/docs\/guides\/revert-last-git-commit\/#optional-create-a-test-repository)\n2. [How to Use the git revert Command on the Last Commit](https:\/\/www.linode.com\/docs\/guides\/revert-last-git-commit\/#how-to-use-the-git-revert-command-on-the-last-commit)\n3. [How to Use the git reset Command to Undo Commits](https:\/\/www.linode.com\/docs\/guides\/revert-last-git-commit\/#how-to-use-the-git-reset-command-to-undo-commits)\n   1. [Differences Between Reset and Revert](https:\/\/www.linode.com\/docs\/guides\/revert-last-git-commit\/#differences-between-reset-and-revert)\n4. [Conclusion](https:\/\/www.linode.com\/docs\/guides\/revert-last-git-commit\/#conclusion)\n5. [More Information](https:\/\/www.linode.com\/docs\/guides\/revert-last-git-commit\/#more-information)\n\n- [Cloud Guides & Tutorials]()\n  \n  - [Akamai + Linode]()\n  - [Applications]()\n  - [Audiences]()\n  - [Concentrations]()\n  - [Databases]()\n  - [Development]()\n    \n    - [Install and Use the Deno Javascript Runtime (Node.js Alternative)]()\n    - [Two Scopes of Exception-Handling]()\n    - [Architectures]()\n    - [Awk]()\n    - [Bash]()\n    - [Bug Management and Tracking]()\n    - [C and C++]()\n    - [Continuous Integration]()\n    - [Clojure]()\n    - [Software Architecture Concepts]()\n    - [Data Visualization]()\n    - [Web Application Frameworks]()\n    - [Go]()\n    - [GraphQL]()\n    - [Internet of Things]()\n    - [Java]()\n    - [Javascript]()\n    - [Julia]()\n    - [Next.js]()\n    - [Node.js]()\n    - [Perl]()\n    - [Python]()\n    - [R]()\n    - [React]()\n    - [Ruby on Rails]()\n    - [Rust]()\n    - [Tips and Tricks]()\n    - [Version Control]()\n      \n      - [Backing up Gitlab on Linode Object Storage]()\n      - [Create Git Aliases to Quickly Run Git or Shell Commands]()\n      - [Getting Started with Git]()\n      - [Getting Started with GitHub]()\n      - [How to Install Git and Clone a GitHub Repository]()\n      - [How to Remove a Remote Git]()\n      - [How to Rename a Git Branch]()\n      - [How to Use a GitLab Runner with Machine Driver and Object Storage]()\n      - [Install and Use the Subversion CLI Client]()\n      - [Install Apache Subversion on Ubuntu 20.04]()\n      - [Install GitLab on Ubuntu 18.04]()\n      - [Install GitLab with Docker]()\n      - [Installing Git on Linux, Mac or Windows]()\n      - [Introduction to Version Control]()\n      - [Remove Untracked Files in Git]()\n      - [Resolve Merge Conflicts in Git]()\n      - [Revert the Last Commit in Git]()\n      - [Speed up Your Development Process with Turborepo]()\n      - [SVN vs Git: Which Version Control System Should You Use?]()\n      - [Switching Git Branches]()\n      - [Unbundling NGINX from Omnibus Gitlab]()\n      - [Undo a Git Commit]()\n      - [Use .gitignore to Ignore Specific Files and Folders]()\n      - [Using the Git Rebase Command]()\n      - [See All 30 Version Control Guides](https:\/\/www.linode.com\/docs\/guides\/development\/version-control\/)\n    - [Web Frameworks]()\n    - [Web Assembly]()\n  - [Email Server Guides]()\n  - [Game Servers]()\n  - [Kubernetes]()\n  - [Languages]()\n  - [IPs, Networking & Domains]()\n  - [Linode Platform]()\n  - [Quick Answers]()\n  - [Security, Upgrades & Backups]()\n  - [Tools & Reference]()\n  - [Uptime & Analytics]()\n  - [Web Server Guides]()\n  - [Website Guides]()\n- [Reference Architectures]()\n- [Marketplace Docs]()\n- [Products]()\n- [API]()\n- [Blog]()\n- [Content Resources]()\n\nFiltered by search term\n\n1. [Docs Home](https:\/\/www.linode.com\/docs\/)\n\nList\n\nSections\n\nTiles\n\nProduct docs and API reference are now on Akamai TechDocs.  \n[Search product docs. Search for “” in product docs.]()  \n[Search API reference. Search for “” in API reference.]()\n\n# Search Results\nresults matching\n\nresults\n## No Results\n[![Article image]()]()\n\nPrevious\n\nNext\n\n## Filters\nFilters (  )\n\n####\nAll\n\n####\nAdd tags\n\nAll\n\n####\nAdd authors\n\nAll\n\n1. [Docs Home](https:\/\/www.linode.com\/docs\/)\n2. [Guides](https:\/\/www.linode.com\/docs\/guides\/)\n3. [Development](https:\/\/www.linode.com\/docs\/guides\/development\/)\n4. [Version Control](https:\/\/www.linode.com\/docs\/guides\/development\/version-control\/)\n\n# Revert the Last Commit in Git\nUpdated\n\nFebruary 15, 2024\n\nOriginally authored by [Nathaniel Stickman](https:\/\/www.linode.com\/docs\/contributors\/nathaniel-stickman\/)\n\n- [Report an Issue]()\n- [View File](https:\/\/github.com\/linode\/docs\/blob\/develop\/docs\/guides\/development\/version-control\/revert-last-git-commit\/index.md)\n- [Edit File]()\n\n- [Share on Twitter]()\n- [Share on Facebook]()\n- [Share on Hacker News]()\n\n> **Traducciones al Español**\n> \n> Estamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso.\n\n[Create a Linode account]() to try this guide with a \\$100 credit.\n\nThis credit will be applied to any valid services used during your first 60 days.\n\nGit is a widely used Version Control System (VCS) known for its versatility. It utilizes local clones of central repositories and keeps track of every commit so changes can be rolled back as needed.\n\nYou might need that recoverability after an inadvertent commit or to undo a commit for any reason. This tutorial shows you how to use the `git` command line utility to revert a commit. It covers methods using both the `git revert` and `git reset` commands and explains the differences.\n\nLearn more about Git generally in our guide [Git vs SVN: Pros and Cons of Each Version Control System](https:\/\/www.linode.com\/docs\/guides\/svn-vs-git\/#what-is-the-git-version-control-system). For a more general, and thorough, coverage of reverting Git commits, take a look at our guide on [How to Undo a Git Commit](https:\/\/www.linode.com\/docs\/guides\/how-to-undo-git-commit\/).\n\n## Optional: Create a Test Repository\nIf you’d like to test reverting and resetting in a separate repository from one you actively work in, follow the steps below. This will set up an example Git repository similar to the one used for the examples in this tutorial. The commit IDs may be different, but the contents of the repository should otherwise be the same.\n\nThe steps presume you have already installed Git and done basic configuration (e.g. user email address and name). If you have not done this yet, you can learn how in our guide [How to Install Git and Clone a GitHub Repository](https:\/\/www.linode.com\/docs\/guides\/how-to-install-git-and-clone-a-github-repository\/).\n\n1. Create a new directory for your Git repository, and change it into that directory. Here, the new directory, `git-example` is created in the current user’s home directory.\n   ```\n   mkdir ~\/git-example\ncd ~\/git-example\n   ```\n   From here on, you should execute the given commands while working in this directory.\n2. Initialize the new Git repository.\n   ```\n   git init\n   ```\n3. Use the `touch` command to create some new empty files.\n   ```\n   touch example-file-1.txt\ntouch example-file-2.txt\n   ```\n4. Add the files to the Git staging area, then commit the staged changes.\n   ```\n   git add .\ngit commit -m \"Initialized repo.\"\n   ```\n5. Make some changes to the first file, adding some content to it. Then stage and commit those changes using the following commands:\n   ```\n   echo \"Some example text for the first file.\" >> example-file-1.txt\ngit add example-file-1.txt\ngit commit -m \"Added text to first file.\"\n   ```\n6. Do the same for the second file.\n   ```\n   echo \"Some example text for the second file.\" >> example-file-2.txt\ngit add example-file-2.txt\ngit commit -m \"Added text to second file.\"\n   ```\n7. You now have a Git repository with a couple of files and several commits, which you can see listed with the following command:\n   ```\n   git log --oneline\n   ```\n   The output of the command looks like the following:\n   ```\n   f4391b2 (HEAD -> master) Added text to second file.\ne3c534a Added text to first file.\n0b24777 Initialized repo.\n   ```\n## How to Use the `git revert` Command on the Last Commit\nGit revert undoes a commit by comparing the changes made in that commit to the repository’s previous state. It then creates a new commit that reverts the changes.\n\nTo use the `git revert` command, you first need the ID for that commit. You can get this with the `git log` command. Here, the command is used with the `--oneline` option to make each commit display on a single line:\n```\ngit log --oneline\n```\n```\nf4391b2 (HEAD -> master) Added text to second file.\ne3c534a Added text to first file.\n0b24777 Initialized repo.\n```\nThe line at the top of the output, with an ID of `f4391b2` in this example, represents the last commit. You can revert that commit using the `revert` command with that commit’s ID, as shown here:\n```\ngit revert f4391b2\n```\nGit starts a new commit to revert the changes. It may present you with a text editor allowing you to edit the description for the new commit. When you are satisfied with the description, exit the text editor to complete the reversion.\n```\n[master e86542a] Revert \"Added text to second file.\"\n 1 file changed, 1 deletion(-)\n```\nRunning the `git log` command again shows that there is now a new commit to revert the previous commit:\n```\ngit log --oneline\n```\n```\ne86542a (HEAD -> master) Revert \"Added text to second file.\"\nf4391b2 Added text to second file.\ne3c534a Added text to first file.\n0b24777 Initialized repo.\n```\nIf you view the affected file, you can see that the changes have been reversed. In this case, that is `example-file-2.txt`:\n```\ncat example-file-2.txt\n```\n## How to Use the `git reset` Command to Undo Commits\nGit reset can also be used to revert the last commit. The command is more powerful than `git revert` and works by removing commits entirely from the repository’s commit history. Essentially, reset “rewinds” you to a previous commit, eliminating later commits and history along the way.\n\nWith the `git reset` command, you have access to the `HEAD~1` alias. This alias stands in for the ID of the previous commit, providing easy access when trying to revert to the last commit.\n\nThe `git reset` command comes with three flags that define how the command deals with changed files in the working directory and staging area.\n\n- Use the `--soft` option to roll back to a previous commit, while preserving file changes in the working directory and staging area.\n  ```\n  git reset --soft HEAD~1\n  ```\n- Use the `--hard` option to likewise roll back to a previous commit. However, this option results in all file changes being reverted as well. Changes to files in the working directory as well as staged changes are both discarded.\n  ```\n  git reset --hard HEAD~1\n  ```\n- Use the `--mixed` option to, again, roll back to a previous commit. Here, a middle ground is adopted for file changes. As with the `--hard` option, changes made to files in the working directory are discarded. However, like the `--soft` option, staged changes are preserved.\n  ```\n  git reset --mixed HEAD~1\n  ```\n\nAfter any of the above commands, you can see that the last commit has been removed from the Git commit history:\n```\ngit log --oneline\n```\n```\ne3c534a (HEAD -> master) Added text to first file.\n0b24777 Initialized repo.\n```\n### Differences Between Reset and Revert\nThe main difference between the `git reset` and `git revert` commands is the commit history.\n\nRevert aims to maintain a full commit history, undoing a commit by assessing changes and making a new commit that reverses them. This actually means that this command adds to the commit history. It gives you full transparency to past commits and their reversions.\n\nIn contrast, using reset discards commits even from the commit history, making them impossible to recover later. The `git reset` command can even do the same for local file changes. This option keeps you from seeing reversions and the original commits that are reverted.\n\nGenerally, it is recommended that you use `git revert` for backing out a commit. It keeps a record of the removed commit and leaves the possibility of assessing and accessing the commit history later.\n\nThe `git reset` command should be used sparingly. Take a good look at the situation to ensure that it cannot be remedied by reverting a commit instead of resetting to a previous commit. A reset might be preferred, however, for immediately undoing mistaken commits, when there is less chance that you need options for recovering the changes.\n\n## Conclusion\nThat covers all you need to revert recent Git commits. Moreover, the techniques covered in this tutorial can also help you manage Git commits more generally. The `git revert` command can be useful for precisely removing past commits while retaining your commit history. The `git reset` command, on the other hand, provides a more radical option, completely reverting a repository to a previous commit, including the commit history.\n\nTo keep learning, refer to the links at the beginning of this guide. These give you more on Git generally as well as more on the commands covered in this tutorial. You may also want to look at our entire lineup of [guides on version control](https:\/\/www.linode.com\/docs\/guides\/development\/version-control\/). These cover everything from the fundamentals to particular use cases, and provide steps to deepen your version control knowledge.\n\n## More Information\nYou may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.\n\n- [freeCodeCamp: Git Revert Commit – How to Undo the Last Commit](https:\/\/www.freecodecamp.org\/news\/git-revert-commit-how-to-undo-the-last-commit\/)\n- [TechTarget: How to Revert a Git Commit](https:\/\/www.theserverside.com\/tutorial\/How-to-git-revert-a-commit-A-simple-undo-changes-example)\n\nThis page was originally published on August 18, 2022.\n\n- [Report an Issue]()\n- [View File](https:\/\/github.com\/linode\/docs\/blob\/develop\/docs\/guides\/development\/version-control\/revert-last-git-commit\/index.md)\n- [Edit File]()\n\n- [Share on Twitter]()\n- [Share on Facebook]()\n- [Share on Hacker News]()\n\n***\n***\nJoin the conversation.\n\nRead other comments or post your own below. Comments must be respectful, constructive, and relevant to the topic of the guide. Do not post external links or advertisements. Before posting, consider if your comment would be better addressed by contacting our [Support team](https:\/\/www.linode.com\/support\/) or asking on our [Community Site](https:\/\/www.linode.com\/community\/questions\/).\n\nThe Disqus commenting system for Linode Docs requires the acceptance of Functional Cookies, which allow us to analyze site usage so we can measure and improve performance. To view and create comments for this article, please [update your Cookie Preferences](https:\/\/www.linode.com\/docs\/guides\/revert-last-git-commit\/) on this website and refresh this web page. Please note: You must have JavaScript enabled in your browser.\n\nPlease enable JavaScript to view the \\<a href=http:\/\/disqus.com\/?ref\\_noscript\\>comments powered by Disqus.\\<\/a\\>\n\n[comments powered by Disqus](http:\/\/disqus.com\/)\n\n### On this page\n1. [Optional: Create a Test Repository](https:\/\/www.linode.com\/docs\/guides\/revert-last-git-commit\/#optional-create-a-test-repository)\n2. [How to Use the git revert Command on the Last Commit](https:\/\/www.linode.com\/docs\/guides\/revert-last-git-commit\/#how-to-use-the-git-revert-command-on-the-last-commit)\n3. [How to Use the git reset Command to Undo Commits](https:\/\/www.linode.com\/docs\/guides\/revert-last-git-commit\/#how-to-use-the-git-reset-command-to-undo-commits)\n   1. [Differences Between Reset and Revert](https:\/\/www.linode.com\/docs\/guides\/revert-last-git-commit\/#differences-between-reset-and-revert)\n4. [Conclusion](https:\/\/www.linode.com\/docs\/guides\/revert-last-git-commit\/#conclusion)\n5. [More Information](https:\/\/www.linode.com\/docs\/guides\/revert-last-git-commit\/#more-information)\n\n#### Products\n- [Products Overview](https:\/\/www.linode.com\/products\/)\n- [Essential Compute](https:\/\/www.linode.com\/products\/essential-compute\/)\n- [GPU](https:\/\/www.linode.com\/products\/gpu\/)\n- [Accelerated Compute](https:\/\/www.linode.com\/products\/accelerated-compute\/)\n- [Kubernetes](https:\/\/www.linode.com\/products\/kubernetes\/)\n- [App Platform](https:\/\/www.linode.com\/products\/app-platform\/)\n- [Block Storage](https:\/\/www.linode.com\/products\/block-storage\/)\n- [Object Storage](https:\/\/www.linode.com\/products\/object-storage\/)\n- [Backups](https:\/\/www.linode.com\/products\/backups\/)\n- [Cloud Firewall](https:\/\/www.linode.com\/products\/cloud-firewall\/)\n- [DNS Manager](https:\/\/www.linode.com\/products\/dns-manager\/)\n- [NodeBalancers](https:\/\/www.linode.com\/products\/nodebalancers\/)\n- [Private Networking](https:\/\/www.linode.com\/products\/private-networking\/)\n- [Managed Databases](https:\/\/www.linode.com\/products\/databases\/)\n- [Linode Managed](https:\/\/www.linode.com\/products\/managed\/)\n- [Distributions](https:\/\/www.linode.com\/distributions\/)\n- [Kernels](https:\/\/www.linode.com\/kernels\/)\n\n#### Company\n- [About Akamai](https:\/\/www.akamai.com\/company)\n- [History](https:\/\/www.akamai.com\/company\/company-history)\n- [Leadership](https:\/\/www.akamai.com\/company\/leadership)\n- [Facts and Figures](https:\/\/www.akamai.com\/company\/facts-figures)\n- [Awards](https:\/\/www.akamai.com\/company\/our-awards)\n- [Board of Directors](https:\/\/www.akamai.com\/company\/leadership\/board-of-directors)\n- [Investor Relations](https:\/\/www.ir.akamai.com\/)\n- [Corporate Responsibility](https:\/\/www.akamai.com\/company\/corporate-responsibility)\n- [Ethics](https:\/\/www.akamai.com\/company\/ethics-and-compliance)\n- [Locations](https:\/\/www.akamai.com\/company\/locations)\n- [Vulnerability Reporting](https:\/\/www.akamai.com\/global-services\/support\/vulnerability-reporting)\n- [Accessibility Commitment](https:\/\/www.linode.com\/accessibility\/)\n\n#### Careers\n- [Careers](https:\/\/www.akamai.com\/careers)\n- [Working at Akamai](https:\/\/www.akamai.com\/careers\/working-at-akamai)\n- [Students and Recent Grads](https:\/\/www.akamai.com\/careers\/students-and-recent-graduates)\n- [Workplace Diversity](https:\/\/www.akamai.com\/careers\/workplace-diversity)\n- [Search Jobs](https:\/\/akamaicareers.inflightcloud.com\/search?searchable=%5B%5D&section=aka_ext)\n- [Culture Blog](https:\/\/www.akamai.com\/blog\/culture)\n\n#### Newsroom\n- [Newsroom](https:\/\/www.akamai.com\/newsroom)\n- [Press Releases](https:\/\/www.akamai.com\/newsroom\/press-release)\n- [In the News](https:\/\/www.akamai.com\/newsroom\/in-the-news)\n- [Media Resources](https:\/\/www.akamai.com\/newsroom\/media-resources)\n\n#### Legal & Compliance\n- [Linode Legal](https:\/\/www.linode.com\/legal\/)\n- [Akamai Legal](https:\/\/www.akamai.com\/legal)\n- [Linode Terms of Service (MSA)](https:\/\/www.linode.com\/legal-msa\/)\n- [EU Digital Services Act (DSA)](https:\/\/www.linode.com\/eu-digital-services-act\/)\n- [Information Security Compliance](https:\/\/www.akamai.com\/legal\/compliance)\n- [Privacy Trust Center](https:\/\/www.akamai.com\/legal\/compliance\/privacy-trust-center)\n- [Cookie Settings](https:\/\/www.linode.com\/legal\/manage-cookie-preferences\/)\n\n#### Glossary\n- [What Is Cloud Security?](https:\/\/www.akamai.com\/glossary\/what-is-cloud-security)\n- [What Is Cloud Redundancy?](https:\/\/www.akamai.com\/glossary\/what-is-cloud-redundancy)\n- [What Is Cloud Computing Security?](https:\/\/www.akamai.com\/glossary\/what-is-cloud-computing-security)\n- [What is Cloud Portability?](https:\/\/www.akamai.com\/glossary\/what-is-cloud-portability)\n- [What Is Event-Driven Architecture?](https:\/\/www.akamai.com\/glossary\/what-is-event-driven-architecture)\n- [See all](https:\/\/www.akamai.com\/glossary)\n\n[![Akamai Logo](https:\/\/www.linode.com\/linode\/en\/images\/logo\/akamai-logo.svg)](https:\/\/www.akamai.com\/)\n\n- Cookie Preferences\n- [Support](https:\/\/www.linode.com\/support\/)\n- [Contact Us](https:\/\/www.linode.com\/company\/contact\/)\n- [System Status](https:\/\/status.linode.com\/)\n- [Site Map](https:\/\/www.linode.com\/site-map\/)\n- © 2003-2025 Linode LLC. All rights reserved.","attrs_readable_markdown":"Git is a widely used Version Control System (VCS) known for its versatility. It utilizes local clones of central repositories and keeps track of every commit so changes can be rolled back as needed.\n\nYou might need that recoverability after an inadvertent commit or to undo a commit for any reason. This tutorial shows you how to use the `git` command line utility to revert a commit. It covers methods using both the `git revert` and `git reset` commands and explains the differences.\n\nLearn more about Git generally in our guide [Git vs SVN: Pros and Cons of Each Version Control System](https:\/\/www.linode.com\/docs\/guides\/svn-vs-git\/#what-is-the-git-version-control-system). For a more general, and thorough, coverage of reverting Git commits, take a look at our guide on [How to Undo a Git Commit](https:\/\/www.linode.com\/docs\/guides\/how-to-undo-git-commit\/).\n\n## Optional: Create a Test Repository\nIf you’d like to test reverting and resetting in a separate repository from one you actively work in, follow the steps below. This will set up an example Git repository similar to the one used for the examples in this tutorial. The commit IDs may be different, but the contents of the repository should otherwise be the same.\n\nThe steps presume you have already installed Git and done basic configuration (e.g. user email address and name). If you have not done this yet, you can learn how in our guide [How to Install Git and Clone a GitHub Repository](https:\/\/www.linode.com\/docs\/guides\/how-to-install-git-and-clone-a-github-repository\/).\n\n1. Create a new directory for your Git repository, and change it into that directory. Here, the new directory, `git-example` is created in the current user’s home directory.\n   ```\n   mkdir ~\/git-example\ncd ~\/git-example\n   ```\n   From here on, you should execute the given commands while working in this directory.\n2. Initialize the new Git repository.\n   ```\n   git init\n   ```\n3. Use the `touch` command to create some new empty files.\n   ```\n   touch example-file-1.txt\ntouch example-file-2.txt\n   ```\n4. Add the files to the Git staging area, then commit the staged changes.\n   ```\n   git add .\ngit commit -m \"Initialized repo.\"\n   ```\n5. Make some changes to the first file, adding some content to it. Then stage and commit those changes using the following commands:\n6. Do the same for the second file.\n7. You now have a Git repository with a couple of files and several commits, which you can see listed with the following command:\n   ```\n   git log --oneline\n   ```\n   The output of the command looks like the following:\n   ```\n   f4391b2 (HEAD -> master) Added text to second file.\ne3c534a Added text to first file.\n0b24777 Initialized repo.\n   ```\n## How to Use the `git revert` Command on the Last Commit\nGit revert undoes a commit by comparing the changes made in that commit to the repository’s previous state. It then creates a new commit that reverts the changes.\n\nTo use the `git revert` command, you first need the ID for that commit. You can get this with the `git log` command. Here, the command is used with the `--oneline` option to make each commit display on a single line:\n```\ngit log --oneline\n```\n```\nf4391b2 (HEAD -> master) Added text to second file.\ne3c534a Added text to first file.\n0b24777 Initialized repo.\n```\nThe line at the top of the output, with an ID of `f4391b2` in this example, represents the last commit. You can revert that commit using the `revert` command with that commit’s ID, as shown here:\n```\ngit revert f4391b2\n```\nGit starts a new commit to revert the changes. It may present you with a text editor allowing you to edit the description for the new commit. When you are satisfied with the description, exit the text editor to complete the reversion.\n```\n[master e86542a] Revert \"Added text to second file.\"\n 1 file changed, 1 deletion(-)\n```\nRunning the `git log` command again shows that there is now a new commit to revert the previous commit:\n```\ngit log --oneline\n```\n```\ne86542a (HEAD -> master) Revert \"Added text to second file.\"\nf4391b2 Added text to second file.\ne3c534a Added text to first file.\n0b24777 Initialized repo.\n```\nIf you view the affected file, you can see that the changes have been reversed. In this case, that is `example-file-2.txt`:\n```\ncat example-file-2.txt\n```\n## How to Use the `git reset` Command to Undo Commits\nGit reset can also be used to revert the last commit. The command is more powerful than `git revert` and works by removing commits entirely from the repository’s commit history. Essentially, reset “rewinds” you to a previous commit, eliminating later commits and history along the way.\n\nWith the `git reset` command, you have access to the `HEAD~1` alias. This alias stands in for the ID of the previous commit, providing easy access when trying to revert to the last commit.\n\nThe `git reset` command comes with three flags that define how the command deals with changed files in the working directory and staging area.\n\n- Use the `--soft` option to roll back to a previous commit, while preserving file changes in the working directory and staging area.\n  ```\n  git reset --soft HEAD~1\n  ```\n- Use the `--hard` option to likewise roll back to a previous commit. However, this option results in all file changes being reverted as well. Changes to files in the working directory as well as staged changes are both discarded.\n  ```\n  git reset --hard HEAD~1\n  ```\n- Use the `--mixed` option to, again, roll back to a previous commit. Here, a middle ground is adopted for file changes. As with the `--hard` option, changes made to files in the working directory are discarded. However, like the `--soft` option, staged changes are preserved.\n  ```\n  git reset --mixed HEAD~1\n  ```\n\nAfter any of the above commands, you can see that the last commit has been removed from the Git commit history:\n```\ngit log --oneline\n```\n```\ne3c534a (HEAD -> master) Added text to first file.\n0b24777 Initialized repo.\n```\n### Differences Between Reset and Revert\nThe main difference between the `git reset` and `git revert` commands is the commit history.\n\nRevert aims to maintain a full commit history, undoing a commit by assessing changes and making a new commit that reverses them. This actually means that this command adds to the commit history. It gives you full transparency to past commits and their reversions.\n\nIn contrast, using reset discards commits even from the commit history, making them impossible to recover later. The `git reset` command can even do the same for local file changes. This option keeps you from seeing reversions and the original commits that are reverted.\n\nGenerally, it is recommended that you use `git revert` for backing out a commit. It keeps a record of the removed commit and leaves the possibility of assessing and accessing the commit history later.\n\nThe `git reset` command should be used sparingly. Take a good look at the situation to ensure that it cannot be remedied by reverting a commit instead of resetting to a previous commit. A reset might be preferred, however, for immediately undoing mistaken commits, when there is less chance that you need options for recovering the changes.\n\n## Conclusion\nThat covers all you need to revert recent Git commits. Moreover, the techniques covered in this tutorial can also help you manage Git commits more generally. The `git revert` command can be useful for precisely removing past commits while retaining your commit history. The `git reset` command, on the other hand, provides a more radical option, completely reverting a repository to a previous commit, including the commit history.\n\nTo keep learning, refer to the links at the beginning of this guide. These give you more on Git generally as well as more on the commands covered in this tutorial. You may also want to look at our entire lineup of [guides on version control](https:\/\/www.linode.com\/docs\/guides\/development\/version-control\/). These cover everything from the fundamentals to particular use cases, and provide steps to deepen your version control knowledge.\n\n## More Information\nYou may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials.\n\n- [freeCodeCamp: Git Revert Commit – How to Undo the Last Commit](https:\/\/www.freecodecamp.org\/news\/git-revert-commit-how-to-undo-the-last-commit\/)\n- [TechTarget: How to Revert a Git Commit](https:\/\/www.theserverside.com\/tutorial\/How-to-git-revert-a-commit-A-simple-undo-changes-example)\n\nThis page was originally published on August 18, 2022.","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

1 month 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`	1.1 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://www.linode.com/docs/guides/revert-last-git-commit/
Last Crawled	2026-03-05 20:57:46 (1 month ago)
First Indexed	2022-10-29 04:49:57 (3 years ago)
HTTP Status Code	200
Meta Title	How to Revert the Last Commit in Git \| Linode Docs
Meta Description	Mistakes happen, and the Git version control system has tools to help you navigate them. In this tutorial, learn two methods to undo your most recent Git commit, what sets the methods apart, and when to use them.
Meta Canonical	null
Boilerpipe Text	Git is a widely used Version Control System (VCS) known for its versatility. It utilizes local clones of central repositories and keeps track of every commit so changes can be rolled back as needed. You might need that recoverability after an inadvertent commit or to undo a commit for any reason. This tutorial shows you how to use the git command line utility to revert a commit. It covers methods using both the git revert and git reset commands and explains the differences. Learn more about Git generally in our guide Git vs SVN: Pros and Cons of Each Version Control System . For a more general, and thorough, coverage of reverting Git commits, take a look at our guide on How to Undo a Git Commit . Optional: Create a Test Repository If you’d like to test reverting and resetting in a separate repository from one you actively work in, follow the steps below. This will set up an example Git repository similar to the one used for the examples in this tutorial. The commit IDs may be different, but the contents of the repository should otherwise be the same. The steps presume you have already installed Git and done basic configuration (e.g. user email address and name). If you have not done this yet, you can learn how in our guide How to Install Git and Clone a GitHub Repository . Create a new directory for your Git repository, and change it into that directory. Here, the new directory, git-example is created in the current user’s home directory. mkdir ~/git-example cd ~/git-example From here on, you should execute the given commands while working in this directory. Initialize the new Git repository. git init Use the touch command to create some new empty files. touch example-file-1.txt touch example-file-2.txt Add the files to the Git staging area, then commit the staged changes. git add . git commit -m "Initialized repo." Make some changes to the first file, adding some content to it. Then stage and commit those changes using the following commands: Do the same for the second file. You now have a Git repository with a couple of files and several commits, which you can see listed with the following command: git log --oneline The output of the command looks like the following: f4391b2 (HEAD -> master) Added text to second file. e3c534a Added text to first file. 0b24777 Initialized repo. How to Use the git revert Command on the Last Commit Git revert undoes a commit by comparing the changes made in that commit to the repository’s previous state. It then creates a new commit that reverts the changes. To use the git revert command, you first need the ID for that commit. You can get this with the git log command. Here, the command is used with the --oneline option to make each commit display on a single line: git log --oneline f4391b2 (HEAD -> master) Added text to second file. e3c534a Added text to first file. 0b24777 Initialized repo. The line at the top of the output, with an ID of f4391b2 in this example, represents the last commit. You can revert that commit using the revert command with that commit’s ID, as shown here: git revert f4391b2 Git starts a new commit to revert the changes. It may present you with a text editor allowing you to edit the description for the new commit. When you are satisfied with the description, exit the text editor to complete the reversion. [master e86542a] Revert "Added text to second file." 1 file changed, 1 deletion(-) Running the git log command again shows that there is now a new commit to revert the previous commit: git log --oneline e86542a (HEAD -> master) Revert "Added text to second file." f4391b2 Added text to second file. e3c534a Added text to first file. 0b24777 Initialized repo. If you view the affected file, you can see that the changes have been reversed. In this case, that is example-file-2.txt : cat example-file-2.txt How to Use the git reset Command to Undo Commits Git reset can also be used to revert the last commit. The command is more powerful than git revert and works by removing commits entirely from the repository’s commit history. Essentially, reset “rewinds” you to a previous commit, eliminating later commits and history along the way. With the git reset command, you have access to the HEAD~1 alias. This alias stands in for the ID of the previous commit, providing easy access when trying to revert to the last commit. The git reset command comes with three flags that define how the command deals with changed files in the working directory and staging area. Use the --soft option to roll back to a previous commit, while preserving file changes in the working directory and staging area. git reset --soft HEAD~1 Use the --hard option to likewise roll back to a previous commit. However, this option results in all file changes being reverted as well. Changes to files in the working directory as well as staged changes are both discarded. git reset --hard HEAD~1 Use the --mixed option to, again, roll back to a previous commit. Here, a middle ground is adopted for file changes. As with the --hard option, changes made to files in the working directory are discarded. However, like the --soft option, staged changes are preserved. git reset --mixed HEAD~1 After any of the above commands, you can see that the last commit has been removed from the Git commit history: git log --oneline e3c534a (HEAD -> master) Added text to first file. 0b24777 Initialized repo. Differences Between Reset and Revert The main difference between the git reset and git revert commands is the commit history. Revert aims to maintain a full commit history, undoing a commit by assessing changes and making a new commit that reverses them. This actually means that this command adds to the commit history. It gives you full transparency to past commits and their reversions. In contrast, using reset discards commits even from the commit history, making them impossible to recover later. The git reset command can even do the same for local file changes. This option keeps you from seeing reversions and the original commits that are reverted. Generally, it is recommended that you use git revert for backing out a commit. It keeps a record of the removed commit and leaves the possibility of assessing and accessing the commit history later. The git reset command should be used sparingly. Take a good look at the situation to ensure that it cannot be remedied by reverting a commit instead of resetting to a previous commit. A reset might be preferred, however, for immediately undoing mistaken commits, when there is less chance that you need options for recovering the changes. Conclusion That covers all you need to revert recent Git commits. Moreover, the techniques covered in this tutorial can also help you manage Git commits more generally. The git revert command can be useful for precisely removing past commits while retaining your commit history. The git reset command, on the other hand, provides a more radical option, completely reverting a repository to a previous commit, including the commit history. To keep learning, refer to the links at the beginning of this guide. These give you more on Git generally as well as more on the commands covered in this tutorial. You may also want to look at our entire lineup of guides on version control . These cover everything from the fundamentals to particular use cases, and provide steps to deepen your version control knowledge. More Information You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials. freeCodeCamp: Git Revert Commit – How to Undo the Last Commit TechTarget: How to Revert a Git Commit This page was originally published on August 18, 2022.
Markdown	- [Search](https://www.linode.com/search/) - [Docs](https://techdocs.akamai.com/cloud-computing/docs/welcome) - [Blog](https://www.linode.com/blog/) - [Support](https://www.linode.com/support/) - [Sales](https://www.linode.com/company/contact/) - [Log in](https://login.linode.com/login) [![Akamai Cloud](https://www.linode.com/linode/en/images/logo/akamai-cloud-logo.svg)](https://www.linode.com/) - Explore - Products - Solutions - Pricing - Resources - [Partners](https://www.linode.com/partners/) - [Sign up](https://login.linode.com/signup) - Mobile - Explore - [Lower costs](https://www.linode.com/reduce-cloud-costs/) - [Lower latency](https://www.linode.com/low-latency-applications/) - [Cloud portability](https://www.linode.com/cloud-portability/) - [Global scale](https://www.linode.com/cloud-global-scale/) - [Our platform](https://www.linode.com/global-infrastructure/) - [Support experience](https://www.linode.com/support-experience/) - Products - [Products Overview](https://www.linode.com/products/) - Compute - [Essential Compute](https://www.linode.com/products/essential-compute/) - [GPU](https://www.linode.com/products/gpu/) - [Accelerated Compute](https://www.linode.com/products/accelerated-compute/) - [Kubernetes](https://www.linode.com/products/kubernetes/) - [App Platform](https://www.linode.com/products/app-platform/) - Storage - [Block Storage](https://www.linode.com/products/block-storage/) - [Object Storage](https://www.linode.com/products/object-storage/) - [Backups](https://www.linode.com/products/backups/) - Networking - [Cloud Firewall](https://www.linode.com/products/cloud-firewall/) - [DNS Manager](https://www.linode.com/products/dns-manager/) - [NodeBalancers](https://www.linode.com/products/nodebalancers/) - [Private Networking](https://www.linode.com/products/private-networking/) - Databases - [Managed Databases](https://www.linode.com/products/databases/) - Services - [Linode Managed](https://www.linode.com/products/managed/) - Solutions - [AI inferencing](https://www.linode.com/solutions/ai-inferencing/) - [Ecommerce](https://www.linode.com/solutions/ecommerce/) - [Gaming](https://www.linode.com/solutions/gaming/) - [Managed hosting](https://www.linode.com/solutions/managed-hosting/) - [Media](https://www.linode.com/solutions/media/) - [SaaS](https://www.linode.com/solutions/saas/) - Pricing - [Pricing list](https://www.linode.com/pricing/) - [Cloud computing calculator](https://www.linode.com/pricing/cloud-cost-calculator/) - Resources - [White paper, ebooks, videos…](https://www.linode.com/resources/) - [Developer hub](https://www.linode.com/developers/) - [Documentation](https://techdocs.akamai.com/cloud-computing/docs/welcome) - [Guides](https://www.linode.com/docs/) - [Reference architectures](https://www.linode.com/docs/reference-architecture/) - [Community Q\&A](https://www.linode.com/community/questions/) - [Beta program](https://www.linode.com/green-light/) - [Startup program](https://www.linode.com/startup-programs/) - [Marketplace apps](https://www.linode.com/marketplace/) - [Blog](https://www.linode.com/blog/) - [Events and workshops](https://www.linode.com/events/) - [Partners](https://www.linode.com/partners/) - Company - [About Us](https://www.linode.com/company/about/) - [Newsroom](https://www.akamai.com/newsroom) - [Careers](https://www.akamai.com/careers) - [Legal](https://www.linode.com/legal/) - [Sales](https://www.linode.com/company/contact/) - [System Status](https://status.linode.com/) - Search - [Docs](https://techdocs.akamai.com/cloud-computing/docs/welcome) - [Blog](https://www.linode.com/blog/) - [Resources](https://www.linode.com/resources/) - [Pricing](https://www.linode.com/pricing/) - [Support](https://www.linode.com/support/) - [Sales](https://www.linode.com/company/contact/) - [Log in](https://login.linode.com/login) - [Sign up](https://login.linode.com/signup) ###### Featured [![Hero Forge Craft of Code Header](https://www.linode.com/ns/features/prod/images/hero-forge-craft-of-code-632x279.jpg)Hero Forge Secure, accessible GPU instances. Unleash millions of adventures. Read story](https://www.akamai.com/resources/customer-story/hero-forge) - [Lower costs](https://www.linode.com/reduce-cloud-costs/) - [Lower latency](https://www.linode.com/low-latency-applications/) - [Cloud portability](https://www.linode.com/cloud-portability/) - [Global scale](https://www.linode.com/cloud-global-scale/) - [Our platform](https://www.linode.com/global-infrastructure/) - [Support experience](https://www.linode.com/support-experience/) ###### Featured [![GPU acceleration](https://www.linode.com/ns/features/prod/images/gpu-438.png)GPU acceleration Power AI and media workloads with on-demand NVIDIA™ GPUs at cost-effective pricing. View product details](https://www.linode.com/products/gpu/) [View all products](https://www.linode.com/products/) ###### Compute - [Essential Compute](https://www.linode.com/products/essential-compute/) - [GPU](https://www.linode.com/products/gpu/) - [Accelerated Compute](https://www.linode.com/products/accelerated-compute/) - [Kubernetes](https://www.linode.com/products/kubernetes/) - [App Platform](https://www.linode.com/products/app-platform/) ###### Storage - [Block Storage](https://www.linode.com/products/block-storage/) - [Object Storage](https://www.linode.com/products/object-storage/) - [Backups](https://www.linode.com/products/backups/) ###### Networking - [Cloud Firewall](https://www.linode.com/products/cloud-firewall/) - [DNS Manager](https://www.linode.com/products/dns-manager/) - [NodeBalancers](https://www.linode.com/products/nodebalancers/) - [Private Networking](https://www.linode.com/products/private-networking/) ###### Databases - [Managed Databases](https://www.linode.com/products/databases/) ###### Services - [Linode Managed](https://www.linode.com/products/managed/) ###### Featured [![Portability in the Cloud: Best Practices for Building SaaS-Based Applications](https://www.linode.com/ns/features/prod/images/MRK-4404-Portability-i632x217-px.jpg)Portability in the cloud Best practices for building SaaS-based applications. Get your copy](https://www.linode.com/resources/ebook/cloud-portability-saas-applications/) ###### Solutions - [AI inferencing](https://www.linode.com/solutions/ai-inferencing/) - [Ecommerce](https://www.linode.com/solutions/ecommerce/) - [Gaming](https://www.linode.com/solutions/gaming/) - [Managed hosting](https://www.linode.com/solutions/managed-hosting/) - [Media](https://www.linode.com/solutions/media/) - [SaaS](https://www.linode.com/solutions/saas/) ###### Featured [![Cloud Pricing Calculator](https://www.linode.com/ns/features/prod/images/Cloud_Pricing_MockUp2-416x376.png)Cloud computing calculator Estimate your cloud costs. Price and configure cloud features to match your needs. Launch calculator](https://www.linode.com/pricing/cloud-cost-calculator/) ###### Pricing - [Pricing list](https://www.linode.com/pricing/) - [Cloud computing calculator](https://www.linode.com/pricing/cloud-cost-calculator/) ###### Featured [![](https://www.linode.com/ns/features/prod/images/developerHub-submenu-sm.jpg)Developer hub Comprehensive guides, documentation, and endpoints. Everything you need to get started. Visit hub](https://www.linode.com/developers/) ###### Library - [White paper, ebooks, videos…](https://www.linode.com/resources/) ###### Technical Resources - [Developer hub](https://www.linode.com/developers/) - [Documentation](https://techdocs.akamai.com/cloud-computing/docs/welcome) - [Guides](https://www.linode.com/docs/) - [Reference architectures](https://www.linode.com/docs/reference-architecture/) ###### Community - [Community Q\&A](https://www.linode.com/community/questions/) - [Beta program](https://www.linode.com/green-light/) - [Startup program](https://www.linode.com/startup-programs/) ###### Marketplace - [Browse apps](https://www.linode.com/marketplace/) ###### What's New - [Blog](https://www.linode.com/blog/) - [Events and workshops](https://www.linode.com/events/) Explore docs 1. [Docs Home](https://www.linode.com/docs/) 2. [Guides](https://www.linode.com/docs/guides/) 3. [Development](https://www.linode.com/docs/guides/development/) 4. [Version Control](https://www.linode.com/docs/guides/development/version-control/) - On this page On this page ### On this page 1. [Optional: Create a Test Repository](https://www.linode.com/docs/guides/revert-last-git-commit/#optional-create-a-test-repository) 2. [How to Use the git revert Command on the Last Commit](https://www.linode.com/docs/guides/revert-last-git-commit/#how-to-use-the-git-revert-command-on-the-last-commit) 3. [How to Use the git reset Command to Undo Commits](https://www.linode.com/docs/guides/revert-last-git-commit/#how-to-use-the-git-reset-command-to-undo-commits) 1. [Differences Between Reset and Revert](https://www.linode.com/docs/guides/revert-last-git-commit/#differences-between-reset-and-revert) 4. [Conclusion](https://www.linode.com/docs/guides/revert-last-git-commit/#conclusion) 5. [More Information](https://www.linode.com/docs/guides/revert-last-git-commit/#more-information) - [Cloud Guides & Tutorials]() - [Akamai + Linode]() - [Applications]() - [Audiences]() - [Concentrations]() - [Databases]() - [Development]() - [Install and Use the Deno Javascript Runtime (Node.js Alternative)]() - [Two Scopes of Exception-Handling]() - [Architectures]() - [Awk]() - [Bash]() - [Bug Management and Tracking]() - [C and C++]() - [Continuous Integration]() - [Clojure]() - [Software Architecture Concepts]() - [Data Visualization]() - [Web Application Frameworks]() - [Go]() - [GraphQL]() - [Internet of Things]() - [Java]() - [Javascript]() - [Julia]() - [Next.js]() - [Node.js]() - [Perl]() - [Python]() - [R]() - [React]() - [Ruby on Rails]() - [Rust]() - [Tips and Tricks]() - [Version Control]() - [Backing up Gitlab on Linode Object Storage]() - [Create Git Aliases to Quickly Run Git or Shell Commands]() - [Getting Started with Git]() - [Getting Started with GitHub]() - [How to Install Git and Clone a GitHub Repository]() - [How to Remove a Remote Git]() - [How to Rename a Git Branch]() - [How to Use a GitLab Runner with Machine Driver and Object Storage]() - [Install and Use the Subversion CLI Client]() - [Install Apache Subversion on Ubuntu 20.04]() - [Install GitLab on Ubuntu 18.04]() - [Install GitLab with Docker]() - [Installing Git on Linux, Mac or Windows]() - [Introduction to Version Control]() - [Remove Untracked Files in Git]() - [Resolve Merge Conflicts in Git]() - [Revert the Last Commit in Git]() - [Speed up Your Development Process with Turborepo]() - [SVN vs Git: Which Version Control System Should You Use?]() - [Switching Git Branches]() - [Unbundling NGINX from Omnibus Gitlab]() - [Undo a Git Commit]() - [Use .gitignore to Ignore Specific Files and Folders]() - [Using the Git Rebase Command]() - [See All 30 Version Control Guides](https://www.linode.com/docs/guides/development/version-control/) - [Web Frameworks]() - [Web Assembly]() - [Email Server Guides]() - [Game Servers]() - [Kubernetes]() - [Languages]() - [IPs, Networking & Domains]() - [Linode Platform]() - [Quick Answers]() - [Security, Upgrades & Backups]() - [Tools & Reference]() - [Uptime & Analytics]() - [Web Server Guides]() - [Website Guides]() - [Reference Architectures]() - [Marketplace Docs]() - [Products]() - [API]() - [Blog]() - [Content Resources]() Filtered by search term 1. [Docs Home](https://www.linode.com/docs/) List Sections Tiles Product docs and API reference are now on Akamai TechDocs. [Search product docs. Search for “” in product docs.]() [Search API reference. Search for “” in API reference.]() # Search Results results matching results ## No Results [![Article image]()]() Previous Next ## Filters Filters ( ) #### All #### Add tags All #### Add authors All 1. [Docs Home](https://www.linode.com/docs/) 2. [Guides](https://www.linode.com/docs/guides/) 3. [Development](https://www.linode.com/docs/guides/development/) 4. [Version Control](https://www.linode.com/docs/guides/development/version-control/) # Revert the Last Commit in Git Updated February 15, 2024 Originally authored by [Nathaniel Stickman](https://www.linode.com/docs/contributors/nathaniel-stickman/) - [Report an Issue]() - [View File](https://github.com/linode/docs/blob/develop/docs/guides/development/version-control/revert-last-git-commit/index.md) - [Edit File]() - [Share on Twitter]() - [Share on Facebook]() - [Share on Hacker News]() > Traducciones al Español > > Estamos traduciendo nuestros guías y tutoriales al Español. Es posible que usted esté viendo una traducción generada automáticamente. Estamos trabajando con traductores profesionales para verificar las traducciones de nuestro sitio web. Este proyecto es un trabajo en curso. [Create a Linode account]() to try this guide with a \$100 credit. This credit will be applied to any valid services used during your first 60 days. Git is a widely used Version Control System (VCS) known for its versatility. It utilizes local clones of central repositories and keeps track of every commit so changes can be rolled back as needed. You might need that recoverability after an inadvertent commit or to undo a commit for any reason. This tutorial shows you how to use the `git` command line utility to revert a commit. It covers methods using both the `git revert` and `git reset` commands and explains the differences. Learn more about Git generally in our guide [Git vs SVN: Pros and Cons of Each Version Control System](https://www.linode.com/docs/guides/svn-vs-git/#what-is-the-git-version-control-system). For a more general, and thorough, coverage of reverting Git commits, take a look at our guide on [How to Undo a Git Commit](https://www.linode.com/docs/guides/how-to-undo-git-commit/). ## Optional: Create a Test Repository If you’d like to test reverting and resetting in a separate repository from one you actively work in, follow the steps below. This will set up an example Git repository similar to the one used for the examples in this tutorial. The commit IDs may be different, but the contents of the repository should otherwise be the same. The steps presume you have already installed Git and done basic configuration (e.g. user email address and name). If you have not done this yet, you can learn how in our guide [How to Install Git and Clone a GitHub Repository](https://www.linode.com/docs/guides/how-to-install-git-and-clone-a-github-repository/). 1. Create a new directory for your Git repository, and change it into that directory. Here, the new directory, `git-example` is created in the current user’s home directory. ``` mkdir ~/git-example cd ~/git-example ``` From here on, you should execute the given commands while working in this directory. 2. Initialize the new Git repository. ``` git init ``` 3. Use the `touch` command to create some new empty files. ``` touch example-file-1.txt touch example-file-2.txt ``` 4. Add the files to the Git staging area, then commit the staged changes. ``` git add . git commit -m "Initialized repo." ``` 5. Make some changes to the first file, adding some content to it. Then stage and commit those changes using the following commands: ``` echo "Some example text for the first file." >> example-file-1.txt git add example-file-1.txt git commit -m "Added text to first file." ``` 6. Do the same for the second file. ``` echo "Some example text for the second file." >> example-file-2.txt git add example-file-2.txt git commit -m "Added text to second file." ``` 7. You now have a Git repository with a couple of files and several commits, which you can see listed with the following command: ``` git log --oneline ``` The output of the command looks like the following: ``` f4391b2 (HEAD -> master) Added text to second file. e3c534a Added text to first file. 0b24777 Initialized repo. ``` ## How to Use the `git revert` Command on the Last Commit Git revert undoes a commit by comparing the changes made in that commit to the repository’s previous state. It then creates a new commit that reverts the changes. To use the `git revert` command, you first need the ID for that commit. You can get this with the `git log` command. Here, the command is used with the `--oneline` option to make each commit display on a single line: ``` git log --oneline ``` ``` f4391b2 (HEAD -> master) Added text to second file. e3c534a Added text to first file. 0b24777 Initialized repo. ``` The line at the top of the output, with an ID of `f4391b2` in this example, represents the last commit. You can revert that commit using the `revert` command with that commit’s ID, as shown here: ``` git revert f4391b2 ``` Git starts a new commit to revert the changes. It may present you with a text editor allowing you to edit the description for the new commit. When you are satisfied with the description, exit the text editor to complete the reversion. ``` [master e86542a] Revert "Added text to second file." 1 file changed, 1 deletion(-) ``` Running the `git log` command again shows that there is now a new commit to revert the previous commit: ``` git log --oneline ``` ``` e86542a (HEAD -> master) Revert "Added text to second file." f4391b2 Added text to second file. e3c534a Added text to first file. 0b24777 Initialized repo. ``` If you view the affected file, you can see that the changes have been reversed. In this case, that is `example-file-2.txt`: ``` cat example-file-2.txt ``` ## How to Use the `git reset` Command to Undo Commits Git reset can also be used to revert the last commit. The command is more powerful than `git revert` and works by removing commits entirely from the repository’s commit history. Essentially, reset “rewinds” you to a previous commit, eliminating later commits and history along the way. With the `git reset` command, you have access to the `HEAD~1` alias. This alias stands in for the ID of the previous commit, providing easy access when trying to revert to the last commit. The `git reset` command comes with three flags that define how the command deals with changed files in the working directory and staging area. - Use the `--soft` option to roll back to a previous commit, while preserving file changes in the working directory and staging area. ``` git reset --soft HEAD~1 ``` - Use the `--hard` option to likewise roll back to a previous commit. However, this option results in all file changes being reverted as well. Changes to files in the working directory as well as staged changes are both discarded. ``` git reset --hard HEAD~1 ``` - Use the `--mixed` option to, again, roll back to a previous commit. Here, a middle ground is adopted for file changes. As with the `--hard` option, changes made to files in the working directory are discarded. However, like the `--soft` option, staged changes are preserved. ``` git reset --mixed HEAD~1 ``` After any of the above commands, you can see that the last commit has been removed from the Git commit history: ``` git log --oneline ``` ``` e3c534a (HEAD -> master) Added text to first file. 0b24777 Initialized repo. ``` ### Differences Between Reset and Revert The main difference between the `git reset` and `git revert` commands is the commit history. Revert aims to maintain a full commit history, undoing a commit by assessing changes and making a new commit that reverses them. This actually means that this command adds to the commit history. It gives you full transparency to past commits and their reversions. In contrast, using reset discards commits even from the commit history, making them impossible to recover later. The `git reset` command can even do the same for local file changes. This option keeps you from seeing reversions and the original commits that are reverted. Generally, it is recommended that you use `git revert` for backing out a commit. It keeps a record of the removed commit and leaves the possibility of assessing and accessing the commit history later. The `git reset` command should be used sparingly. Take a good look at the situation to ensure that it cannot be remedied by reverting a commit instead of resetting to a previous commit. A reset might be preferred, however, for immediately undoing mistaken commits, when there is less chance that you need options for recovering the changes. ## Conclusion That covers all you need to revert recent Git commits. Moreover, the techniques covered in this tutorial can also help you manage Git commits more generally. The `git revert` command can be useful for precisely removing past commits while retaining your commit history. The `git reset` command, on the other hand, provides a more radical option, completely reverting a repository to a previous commit, including the commit history. To keep learning, refer to the links at the beginning of this guide. These give you more on Git generally as well as more on the commands covered in this tutorial. You may also want to look at our entire lineup of [guides on version control](https://www.linode.com/docs/guides/development/version-control/). These cover everything from the fundamentals to particular use cases, and provide steps to deepen your version control knowledge. ## More Information You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials. - [freeCodeCamp: Git Revert Commit – How to Undo the Last Commit](https://www.freecodecamp.org/news/git-revert-commit-how-to-undo-the-last-commit/) - [TechTarget: How to Revert a Git Commit](https://www.theserverside.com/tutorial/How-to-git-revert-a-commit-A-simple-undo-changes-example) This page was originally published on August 18, 2022. - [Report an Issue]() - [View File](https://github.com/linode/docs/blob/develop/docs/guides/development/version-control/revert-last-git-commit/index.md) - [Edit File]() - [Share on Twitter]() - [Share on Facebook]() - [Share on Hacker News]() * * Join the conversation. Read other comments or post your own below. Comments must be respectful, constructive, and relevant to the topic of the guide. Do not post external links or advertisements. Before posting, consider if your comment would be better addressed by contacting our [Support team](https://www.linode.com/support/) or asking on our [Community Site](https://www.linode.com/community/questions/). The Disqus commenting system for Linode Docs requires the acceptance of Functional Cookies, which allow us to analyze site usage so we can measure and improve performance. To view and create comments for this article, please [update your Cookie Preferences](https://www.linode.com/docs/guides/revert-last-git-commit/) on this website and refresh this web page. Please note: You must have JavaScript enabled in your browser. Please enable JavaScript to view the \<a href=http://disqus.com/?ref\_noscript\>comments powered by Disqus.\</a\> [comments powered by Disqus](http://disqus.com/) ### On this page 1. [Optional: Create a Test Repository](https://www.linode.com/docs/guides/revert-last-git-commit/#optional-create-a-test-repository) 2. [How to Use the git revert Command on the Last Commit](https://www.linode.com/docs/guides/revert-last-git-commit/#how-to-use-the-git-revert-command-on-the-last-commit) 3. [How to Use the git reset Command to Undo Commits](https://www.linode.com/docs/guides/revert-last-git-commit/#how-to-use-the-git-reset-command-to-undo-commits) 1. [Differences Between Reset and Revert](https://www.linode.com/docs/guides/revert-last-git-commit/#differences-between-reset-and-revert) 4. [Conclusion](https://www.linode.com/docs/guides/revert-last-git-commit/#conclusion) 5. [More Information](https://www.linode.com/docs/guides/revert-last-git-commit/#more-information) #### Products - [Products Overview](https://www.linode.com/products/) - [Essential Compute](https://www.linode.com/products/essential-compute/) - [GPU](https://www.linode.com/products/gpu/) - [Accelerated Compute](https://www.linode.com/products/accelerated-compute/) - [Kubernetes](https://www.linode.com/products/kubernetes/) - [App Platform](https://www.linode.com/products/app-platform/) - [Block Storage](https://www.linode.com/products/block-storage/) - [Object Storage](https://www.linode.com/products/object-storage/) - [Backups](https://www.linode.com/products/backups/) - [Cloud Firewall](https://www.linode.com/products/cloud-firewall/) - [DNS Manager](https://www.linode.com/products/dns-manager/) - [NodeBalancers](https://www.linode.com/products/nodebalancers/) - [Private Networking](https://www.linode.com/products/private-networking/) - [Managed Databases](https://www.linode.com/products/databases/) - [Linode Managed](https://www.linode.com/products/managed/) - [Distributions](https://www.linode.com/distributions/) - [Kernels](https://www.linode.com/kernels/) #### Company - [About Akamai](https://www.akamai.com/company) - [History](https://www.akamai.com/company/company-history) - [Leadership](https://www.akamai.com/company/leadership) - [Facts and Figures](https://www.akamai.com/company/facts-figures) - [Awards](https://www.akamai.com/company/our-awards) - [Board of Directors](https://www.akamai.com/company/leadership/board-of-directors) - [Investor Relations](https://www.ir.akamai.com/) - [Corporate Responsibility](https://www.akamai.com/company/corporate-responsibility) - [Ethics](https://www.akamai.com/company/ethics-and-compliance) - [Locations](https://www.akamai.com/company/locations) - [Vulnerability Reporting](https://www.akamai.com/global-services/support/vulnerability-reporting) - [Accessibility Commitment](https://www.linode.com/accessibility/) #### Careers - [Careers](https://www.akamai.com/careers) - [Working at Akamai](https://www.akamai.com/careers/working-at-akamai) - [Students and Recent Grads](https://www.akamai.com/careers/students-and-recent-graduates) - [Workplace Diversity](https://www.akamai.com/careers/workplace-diversity) - [Search Jobs](https://akamaicareers.inflightcloud.com/search?searchable=%5B%5D&section=aka_ext) - [Culture Blog](https://www.akamai.com/blog/culture) #### Newsroom - [Newsroom](https://www.akamai.com/newsroom) - [Press Releases](https://www.akamai.com/newsroom/press-release) - [In the News](https://www.akamai.com/newsroom/in-the-news) - [Media Resources](https://www.akamai.com/newsroom/media-resources) #### Legal & Compliance - [Linode Legal](https://www.linode.com/legal/) - [Akamai Legal](https://www.akamai.com/legal) - [Linode Terms of Service (MSA)](https://www.linode.com/legal-msa/) - [EU Digital Services Act (DSA)](https://www.linode.com/eu-digital-services-act/) - [Information Security Compliance](https://www.akamai.com/legal/compliance) - [Privacy Trust Center](https://www.akamai.com/legal/compliance/privacy-trust-center) - [Cookie Settings](https://www.linode.com/legal/manage-cookie-preferences/) #### Glossary - [What Is Cloud Security?](https://www.akamai.com/glossary/what-is-cloud-security) - [What Is Cloud Redundancy?](https://www.akamai.com/glossary/what-is-cloud-redundancy) - [What Is Cloud Computing Security?](https://www.akamai.com/glossary/what-is-cloud-computing-security) - [What is Cloud Portability?](https://www.akamai.com/glossary/what-is-cloud-portability) - [What Is Event-Driven Architecture?](https://www.akamai.com/glossary/what-is-event-driven-architecture) - [See all](https://www.akamai.com/glossary) [![Akamai Logo](https://www.linode.com/linode/en/images/logo/akamai-logo.svg)](https://www.akamai.com/) - Cookie Preferences - [Support](https://www.linode.com/support/) - [Contact Us](https://www.linode.com/company/contact/) - [System Status](https://status.linode.com/) - [Site Map](https://www.linode.com/site-map/) - © 2003-2025 Linode LLC. All rights reserved.
Readable Markdown	Git is a widely used Version Control System (VCS) known for its versatility. It utilizes local clones of central repositories and keeps track of every commit so changes can be rolled back as needed. You might need that recoverability after an inadvertent commit or to undo a commit for any reason. This tutorial shows you how to use the `git` command line utility to revert a commit. It covers methods using both the `git revert` and `git reset` commands and explains the differences. Learn more about Git generally in our guide [Git vs SVN: Pros and Cons of Each Version Control System](https://www.linode.com/docs/guides/svn-vs-git/#what-is-the-git-version-control-system). For a more general, and thorough, coverage of reverting Git commits, take a look at our guide on [How to Undo a Git Commit](https://www.linode.com/docs/guides/how-to-undo-git-commit/). ## Optional: Create a Test Repository If you’d like to test reverting and resetting in a separate repository from one you actively work in, follow the steps below. This will set up an example Git repository similar to the one used for the examples in this tutorial. The commit IDs may be different, but the contents of the repository should otherwise be the same. The steps presume you have already installed Git and done basic configuration (e.g. user email address and name). If you have not done this yet, you can learn how in our guide [How to Install Git and Clone a GitHub Repository](https://www.linode.com/docs/guides/how-to-install-git-and-clone-a-github-repository/). 1. Create a new directory for your Git repository, and change it into that directory. Here, the new directory, `git-example` is created in the current user’s home directory. ``` mkdir ~/git-example cd ~/git-example ``` From here on, you should execute the given commands while working in this directory. 2. Initialize the new Git repository. ``` git init ``` 3. Use the `touch` command to create some new empty files. ``` touch example-file-1.txt touch example-file-2.txt ``` 4. Add the files to the Git staging area, then commit the staged changes. ``` git add . git commit -m "Initialized repo." ``` 5. Make some changes to the first file, adding some content to it. Then stage and commit those changes using the following commands: 6. Do the same for the second file. 7. You now have a Git repository with a couple of files and several commits, which you can see listed with the following command: ``` git log --oneline ``` The output of the command looks like the following: ``` f4391b2 (HEAD -> master) Added text to second file. e3c534a Added text to first file. 0b24777 Initialized repo. ``` ## How to Use the `git revert` Command on the Last Commit Git revert undoes a commit by comparing the changes made in that commit to the repository’s previous state. It then creates a new commit that reverts the changes. To use the `git revert` command, you first need the ID for that commit. You can get this with the `git log` command. Here, the command is used with the `--oneline` option to make each commit display on a single line: ``` git log --oneline ``` ``` f4391b2 (HEAD -> master) Added text to second file. e3c534a Added text to first file. 0b24777 Initialized repo. ``` The line at the top of the output, with an ID of `f4391b2` in this example, represents the last commit. You can revert that commit using the `revert` command with that commit’s ID, as shown here: ``` git revert f4391b2 ``` Git starts a new commit to revert the changes. It may present you with a text editor allowing you to edit the description for the new commit. When you are satisfied with the description, exit the text editor to complete the reversion. ``` [master e86542a] Revert "Added text to second file." 1 file changed, 1 deletion(-) ``` Running the `git log` command again shows that there is now a new commit to revert the previous commit: ``` git log --oneline ``` ``` e86542a (HEAD -> master) Revert "Added text to second file." f4391b2 Added text to second file. e3c534a Added text to first file. 0b24777 Initialized repo. ``` If you view the affected file, you can see that the changes have been reversed. In this case, that is `example-file-2.txt`: ``` cat example-file-2.txt ``` ## How to Use the `git reset` Command to Undo Commits Git reset can also be used to revert the last commit. The command is more powerful than `git revert` and works by removing commits entirely from the repository’s commit history. Essentially, reset “rewinds” you to a previous commit, eliminating later commits and history along the way. With the `git reset` command, you have access to the `HEAD~1` alias. This alias stands in for the ID of the previous commit, providing easy access when trying to revert to the last commit. The `git reset` command comes with three flags that define how the command deals with changed files in the working directory and staging area. - Use the `--soft` option to roll back to a previous commit, while preserving file changes in the working directory and staging area. ``` git reset --soft HEAD~1 ``` - Use the `--hard` option to likewise roll back to a previous commit. However, this option results in all file changes being reverted as well. Changes to files in the working directory as well as staged changes are both discarded. ``` git reset --hard HEAD~1 ``` - Use the `--mixed` option to, again, roll back to a previous commit. Here, a middle ground is adopted for file changes. As with the `--hard` option, changes made to files in the working directory are discarded. However, like the `--soft` option, staged changes are preserved. ``` git reset --mixed HEAD~1 ``` After any of the above commands, you can see that the last commit has been removed from the Git commit history: ``` git log --oneline ``` ``` e3c534a (HEAD -> master) Added text to first file. 0b24777 Initialized repo. ``` ### Differences Between Reset and Revert The main difference between the `git reset` and `git revert` commands is the commit history. Revert aims to maintain a full commit history, undoing a commit by assessing changes and making a new commit that reverses them. This actually means that this command adds to the commit history. It gives you full transparency to past commits and their reversions. In contrast, using reset discards commits even from the commit history, making them impossible to recover later. The `git reset` command can even do the same for local file changes. This option keeps you from seeing reversions and the original commits that are reverted. Generally, it is recommended that you use `git revert` for backing out a commit. It keeps a record of the removed commit and leaves the possibility of assessing and accessing the commit history later. The `git reset` command should be used sparingly. Take a good look at the situation to ensure that it cannot be remedied by reverting a commit instead of resetting to a previous commit. A reset might be preferred, however, for immediately undoing mistaken commits, when there is less chance that you need options for recovering the changes. ## Conclusion That covers all you need to revert recent Git commits. Moreover, the techniques covered in this tutorial can also help you manage Git commits more generally. The `git revert` command can be useful for precisely removing past commits while retaining your commit history. The `git reset` command, on the other hand, provides a more radical option, completely reverting a repository to a previous commit, including the commit history. To keep learning, refer to the links at the beginning of this guide. These give you more on Git generally as well as more on the commands covered in this tutorial. You may also want to look at our entire lineup of [guides on version control](https://www.linode.com/docs/guides/development/version-control/). These cover everything from the fundamentals to particular use cases, and provide steps to deepen your version control knowledge. ## More Information You may wish to consult the following resources for additional information on this topic. While these are provided in the hope that they will be useful, please note that we cannot vouch for the accuracy or timeliness of externally hosted materials. - [freeCodeCamp: Git Revert Commit – How to Undo the Last Commit](https://www.freecodecamp.org/news/git-revert-commit-how-to-undo-the-last-commit/) - [TechTarget: How to Revert a Git Commit](https://www.theserverside.com/tutorial/How-to-git-revert-a-commit-A-simple-undo-changes-example) This page was originally published on August 18, 2022.
Shard	95 (laksa)
Root Hash	1749289081436496295
Unparsed URL	com,linode!www,/docs/guides/revert-last-git-commit/ s443