🕷️ Crawler Inspector

URL Lookup

Direct Parameter Lookup

Raw Queries and Responses

1. Shard Calculation

Query:

Response:

Calculated Shard: 54 (from laksa005)

2. Crawled Status Check

Query:

curl -X POST \
  'http://laksa054.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://git-scm.com/book/en/v2/Git-Basics-Undoing-Things\')), getAhrefsUnparsedNoserviceFromURL(\'https://git-scm.com/book/en/v2/Git-Basics-Undoing-Things\'))) FORMAT JSONEachRow'

Response:

{"found_url":"https:\/\/git-scm.com\/book\/en\/v2\/Git-Basics-Undoing-Things","crawl_time":1775476229,"first_indexed_time":1414456633,"http_code":200,"src_unparsed":"com,git-scm!\/book\/en\/v2\/Git-Basics-Undoing-Things s443","src_root_hash":"7104038400628677254","history_drop_reason":null,"meta_title":"Git - Undoing Things","meta_descriptions":[],"attrs_boilerpipe_text":"At any stage, you may want to undo something.\nHere, we’ll review a few basic tools for undoing changes that you’ve made.\nBe careful, because you can’t always undo some of these undos.\nThis is one of the few areas in Git where you may lose some work if you do it wrong.\nOne of the common undos takes place when you commit too early and possibly forget to add some files, or you mess up your commit message.\nIf you want to redo that commit, make the additional changes you forgot, stage them, and commit again using the\n--amend\noption:\n$ git commit --amend\nThis command takes your staging area and uses it for the commit.\nIf you’ve made no changes since your last commit (for instance, you run this command immediately after your previous commit), then your snapshot will look exactly the same, and all you’ll change is your commit message.\nThe same commit-message editor fires up, but it already contains the message of your previous commit.\nYou can edit the message the same as always, but it overwrites your previous commit.\nAs an example, if you commit and then realize you forgot to stage the changes in a file you wanted to add to this commit, you can do something like this:\n$ git commit -m 'Initial commit'\n$ git add forgotten_file\n$ git commit --amend\nYou end up with a single commit — the second commit replaces the results of the first.\nNote\nIt’s important to understand that when you’re amending your last commit, you’re not so much fixing it as\nreplacing\nit entirely with a new, improved commit that pushes the old commit out of the way and puts the new commit in its place.\nEffectively, it’s as if the previous commit never happened, and it won’t show up in your repository history.\nThe obvious value to amending commits is to make minor improvements to your last commit, without cluttering your repository history with commit messages of the form, “Oops, forgot to add a file” or “Darn, fixing a typo in last commit”.\nNote\nOnly amend commits that are still local and have not been pushed somewhere.\nAmending previously pushed commits and force pushing the branch will cause problems for your collaborators.\nFor more on what happens when you do this and how to recover if you’re on the receiving end read\nThe Perils of Rebasing\n.\nUnstaging a Staged File\nThe next two sections demonstrate how to work with your staging area and working directory changes.\nThe nice part is that the command you use to determine the state of those two areas also reminds you how to undo changes to them.\nFor example, let’s say you’ve changed two files and want to commit them as two separate changes, but you accidentally type\ngit add *\nand stage them both.\nHow can you unstage one of the two?\nThe\ngit status\ncommand reminds you:\n$ git add *\n$ git status\nOn branch master\nChanges to be committed:\n  (use \"git reset HEAD <file>...\" to unstage)\n\n    renamed:    README.md -> README\n    modified:   CONTRIBUTING.md\nRight below the “Changes to be committed” text, it says use\ngit reset HEAD <file>…\nto unstage.\nSo, let’s use that advice to unstage the\nCONTRIBUTING.md\nfile:\n$ git reset HEAD CONTRIBUTING.md\nUnstaged changes after reset:\nM\tCONTRIBUTING.md\n$ git status\nOn branch master\nChanges to be committed:\n  (use \"git reset HEAD <file>...\" to unstage)\n\n    renamed:    README.md -> README\n\nChanges not staged for commit:\n  (use \"git add <file>...\" to update what will be committed)\n  (use \"git checkout -- <file>...\" to discard changes in working directory)\n\n    modified:   CONTRIBUTING.md\nThe command is a bit strange, but it works.\nThe\nCONTRIBUTING.md\nfile is modified but once again unstaged.\nNote\nIt’s true that\ngit reset\ncan be a dangerous command, especially if you provide the\n--hard\nflag.\nHowever, in the scenario described above, the file in your working directory is not touched, so it’s relatively safe.\nFor now this magic invocation is all you need to know about the\ngit reset\ncommand.\nWe’ll go into much more detail about what\nreset\ndoes and how to master it to do really interesting things in\nReset Demystified\n.\nUnmodifying a Modified File\nWhat if you realize that you don’t want to keep your changes to the\nCONTRIBUTING.md\nfile?\nHow can you easily unmodify it — revert it back to what it looked like when you last committed (or initially cloned, or however you got it into your working directory)?\nLuckily,\ngit status\ntells you how to do that, too.\nIn the last example output, the unstaged area looks like this:\nChanges not staged for commit:\n  (use \"git add <file>...\" to update what will be committed)\n  (use \"git checkout -- <file>...\" to discard changes in working directory)\n\n    modified:   CONTRIBUTING.md\nIt tells you pretty explicitly how to discard the changes you’ve made.\nLet’s do what it says:\n$ git checkout -- CONTRIBUTING.md\n$ git status\nOn branch master\nChanges to be committed:\n  (use \"git reset HEAD <file>...\" to unstage)\n\n    renamed:    README.md -> README\nYou can see that the changes have been reverted.\nImportant\nIt’s important to understand that\ngit checkout -- <file>\nis a dangerous command.\nAny local changes you made to that file are gone — Git just replaced that file with the last staged or committed version.\nDon’t ever use this command unless you absolutely know that you don’t want those unsaved local changes.\nIf you would like to keep the changes you’ve made to that file but still need to get it out of the way for now, we’ll go over stashing and branching in\nGit Branching\n; these are generally better ways to go.\nRemember, anything that is\ncommitted\nin Git can almost always be recovered.\nEven commits that were on branches that were deleted or commits that were overwritten with an\n--amend\ncommit can be recovered (see\nData Recovery\nfor data recovery).\nHowever, anything you lose that was never committed is likely never to be seen again.\nUndoing things with git restore\nGit version 2.23.0 introduced a new command:\ngit restore\n.\nIt’s basically an alternative to\ngit reset\nwhich we just covered.\nFrom Git version 2.23.0 onwards, Git will use\ngit restore\ninstead of\ngit reset\nfor many undo operations.\nLet’s retrace our steps, and undo things with\ngit restore\ninstead of\ngit reset\n.\nUnstaging a Staged File with git restore\nThe next two sections demonstrate how to work with your staging area and working directory changes with\ngit restore\n.\nThe nice part is that the command you use to determine the state of those two areas also reminds you how to undo changes to them.\nFor example, let’s say you’ve changed two files and want to commit them as two separate changes, but you accidentally type\ngit add *\nand stage them both.\nHow can you unstage one of the two?\nThe\ngit status\ncommand reminds you:\n$ git add *\n$ git status\nOn branch master\nChanges to be committed:\n  (use \"git restore --staged <file>...\" to unstage)\n\tmodified:   CONTRIBUTING.md\n\trenamed:    README.md -> README\nRight below the “Changes to be committed” text, it says use\ngit restore --staged <file>…\nto unstage.\nSo, let’s use that advice to unstage the\nCONTRIBUTING.md\nfile:\n$ git restore --staged CONTRIBUTING.md\n$ git status\nOn branch master\nChanges to be committed:\n  (use \"git restore --staged <file>...\" to unstage)\n\trenamed:    README.md -> README\n\nChanges not staged for commit:\n  (use \"git add <file>...\" to update what will be committed)\n  (use \"git restore <file>...\" to discard changes in working directory)\n\tmodified:   CONTRIBUTING.md\nThe\nCONTRIBUTING.md\nfile is modified but once again unstaged.\nUnmodifying a Modified File with git restore\nWhat if you realize that you don’t want to keep your changes to the\nCONTRIBUTING.md\nfile?\nHow can you easily unmodify it — revert it back to what it looked like when you last committed (or initially cloned, or however you got it into your working directory)?\nLuckily,\ngit status\ntells you how to do that, too.\nIn the last example output, the unstaged area looks like this:\nChanges not staged for commit:\n  (use \"git add <file>...\" to update what will be committed)\n  (use \"git restore <file>...\" to discard changes in working directory)\n\tmodified:   CONTRIBUTING.md\nIt tells you pretty explicitly how to discard the changes you’ve made.\nLet’s do what it says:\n$ git restore CONTRIBUTING.md\n$ git status\nOn branch master\nChanges to be committed:\n  (use \"git restore --staged <file>...\" to unstage)\n\trenamed:    README.md -> README\nImportant\nIt’s important to understand that\ngit restore <file>\nis a dangerous command.\nAny local changes you made to that file are gone — Git just replaced that file with the last staged or committed version.\nDon’t ever use this command unless you absolutely know that you don’t want those unsaved local changes.","attrs_markdown":"[![Git](https:\/\/git-scm.com\/images\/logo@2x.png)](https:\/\/git-scm.com\/) \\--distributed-is-the-new-centralized\n\n![](https:\/\/git-scm.com\/images\/dark-mode.svg)\n\n- [About](https:\/\/git-scm.com\/about)\n  - [Trademark](https:\/\/git-scm.com\/about\/trademark)\n- [Learn](https:\/\/git-scm.com\/learn)\n  - [Book](https:\/\/git-scm.com\/book)\n  - [Cheat Sheet](https:\/\/git-scm.com\/cheat-sheet)\n  - [Videos](https:\/\/git-scm.com\/videos)\n  - [External Links](https:\/\/git-scm.com\/doc\/ext)\n- [Tools](https:\/\/git-scm.com\/tools)\n  - [Command Line](https:\/\/git-scm.com\/tools\/command-line)\n  - [GUIs](https:\/\/git-scm.com\/tools\/guis)\n  - [Hosting](https:\/\/git-scm.com\/tools\/hosting)\n- [Reference](https:\/\/git-scm.com\/docs)\n- [Install](https:\/\/git-scm.com\/install\/linux)\n- [Community](https:\/\/git-scm.com\/community)\n***\nThis book is available in [English](https:\/\/git-scm.com\/book\/en\/v2\/Git-Basics-Undoing-Things).\n\nFull translation available in\n\n|   |\n|---|\n| [azərbaycan dili](https:\/\/git-scm.com\/book\/az\/v2\/Git%E2%80%99in-%C6%8Fsaslar%C4%B1-L%C9%99%C4%9Fv-Edil%C9%99n-%C4%B0%C5%9Fl%C9%99r-Geri-qaytar%C4%B1lan), |\n| [български език](https:\/\/git-scm.com\/book\/bg\/v2\/%D0%9E%D1%81%D0%BD%D0%BE%D0%B2%D0%B8-%D0%BD%D0%B0-Git-%D0%92%D1%8A%D0%B7%D1%81%D1%82%D0%B0%D0%BD%D0%BE%D0%B2%D1%8F%D0%B2%D0%B0%D0%BD%D0%B5-%D0%BD%D0%B0-%D0%BD%D0%B0%D0%BF%D1%80%D0%B0%D0%B2%D0%B5%D0%BD%D0%B8-%D0%B4%D0%B5%D0%B9%D1%81%D1%82%D0%B2%D0%B8%D1%8F), |\n| [Deutsch](https:\/\/git-scm.com\/book\/de\/v2\/Git-Grundlagen-Ungewollte-%C3%84nderungen-r%C3%BCckg%C3%A4ngig-machen), |\n| [Español](https:\/\/git-scm.com\/book\/es\/v2\/Fundamentos-de-Git-Deshacer-Cosas), |\n| [فارسی](https:\/\/git-scm.com\/book\/fa\/v2\/%D9%85%D9%82%D8%AF%D9%85%D8%A7%D8%AA-%DA%AF%DB%8C%D8%AA-git-basics-chapter-%D8%A8%D8%A7%D8%B2%DA%AF%D8%B1%D8%AF%D8%A7%D9%86%D8%AF%D9%86-%D8%AA%D8%BA%DB%8C%DB%8C%D8%B1%D8%A7%D8%AA-Undoing-Things), |\n| [Français](https:\/\/git-scm.com\/book\/fr\/v2\/Les-bases-de-Git-Annuler-des-actions), |\n| [Ελληνικά](https:\/\/git-scm.com\/book\/gr\/v2\/%CE%A4%CE%B1-%CE%B8%CE%B5%CE%BC%CE%B5%CE%BB%CE%B9%CF%8E%CE%B4%CE%B7-%CF%83%CF%84%CE%BF%CE%B9%CF%87%CE%B5%CE%AF%CE%B1-%CF%84%CE%BF%CF%85-Git-%CE%91%CE%BD%CE%B1%CE%B9%CF%81%CE%AD%CF%83%CE%B5%CE%B9%CF%82-undoing), |\n| [日本語](https:\/\/git-scm.com\/book\/ja\/v2\/Git-%E3%81%AE%E5%9F%BA%E6%9C%AC-%E4%BD%9C%E6%A5%AD%E3%81%AE%E3%82%84%E3%82%8A%E7%9B%B4%E3%81%97), |\n| [한국어](https:\/\/git-scm.com\/book\/ko\/v2\/Git%EC%9D%98-%EA%B8%B0%EC%B4%88-%EB%90%98%EB%8F%8C%EB%A6%AC%EA%B8%B0), |\n| [Nederlands](https:\/\/git-scm.com\/book\/nl\/v2\/Git-Basics-Dingen-ongedaan-maken), |\n| [Русский](https:\/\/git-scm.com\/book\/ru\/v2\/%D0%9E%D1%81%D0%BD%D0%BE%D0%B2%D1%8B-Git-%D0%9E%D0%BF%D0%B5%D1%80%D0%B0%D1%86%D0%B8%D0%B8-%D0%BE%D1%82%D0%BC%D0%B5%D0%BD%D1%8B), |\n| [Slovenščina](https:\/\/git-scm.com\/book\/sl\/v2\/Osnove-Git-Razveljavljanje-stvari), |\n| [Српски](https:\/\/git-scm.com\/book\/sr\/v2\/%D0%9E%D1%81%D0%BD%D0%BE%D0%B2%D0%B5-%D0%BF%D1%80%D0%BE%D0%B3%D1%80%D0%B0%D0%BC%D0%B0-%D0%93%D0%B8%D1%82-%D0%9E%D0%BF%D0%BE%D0%B7%D0%B8%D0%B2), |\n| [Svenska](https:\/\/git-scm.com\/book\/sv\/v2\/Grunderna-i-Git-%C3%85ngra-saker), |\n| [Tagalog](https:\/\/git-scm.com\/book\/tl\/v2\/Mga-Pangunahing-Kaalaman-sa-Git-Pag-Undo-ng-mga-Bagay), |\n| [Türkçe](https:\/\/git-scm.com\/book\/tr\/v2\/Git-Temelleri-De%C4%9Fi%C5%9Fiklikleri-Geri-Alma). |\n| [Українська](https:\/\/git-scm.com\/book\/uk\/v2\/%D0%9E%D1%81%D0%BD%D0%BE%D0%B2%D0%B8-Git-%D0%A1%D0%BA%D0%B0%D1%81%D1%83%D0%B2%D0%B0%D0%BD%D0%BD%D1%8F-%D1%80%D0%B5%D1%87%D0%B5%D0%B9), |\n| [简体中文](https:\/\/git-scm.com\/book\/zh\/v2\/Git-%E5%9F%BA%E7%A1%80-%E6%92%A4%E6%B6%88%E6%93%8D%E4%BD%9C), |\n\nPartial translations available in\n\n|   |\n|---|\n| [Čeština](https:\/\/git-scm.com\/book\/cs\/v2\/Z%C3%A1klady-pr%C3%A1ce-se-syst%C3%A9mem-Git-N%C3%A1vrat-do-p%C5%99edchoz%C3%ADho-stavu), |\n| [Македонски](https:\/\/git-scm.com\/book\/mk\/v2\/%D0%9E%D1%81%D0%BD%D0%BE%D0%B2%D0%B8%D1%82%D0%B5-%D0%BD%D0%B0-Git-%D0%9F%D0%BE%D0%BD%D0%B8%D1%88%D1%82%D1%83%D0%B2%D0%B0%D1%9A%D0%B5-%D0%BD%D0%B0-%D0%BD%D0%B5%D1%88%D1%82%D0%B0%D1%82%D0%B0), |\n| [Polski](https:\/\/git-scm.com\/book\/pl\/v2\/Podstawy-Gita-Cofanie-zmian), |\n| [Português (Brasil)](https:\/\/git-scm.com\/book\/pt-br\/v2\/Fundamentos-de-Git-Desfazendo-coisas), |\n| [Ўзбекча](https:\/\/git-scm.com\/book\/uz\/v2\/Git-%D0%B0%D1%81%D0%BE%D1%81%D0%BB%D0%B0%D1%80%D0%B8-%D0%8E%D0%B7%D0%B3%D0%B0%D1%80%D0%B8%D1%88%D0%BB%D0%B0%D1%80%D0%BD%D0%B8-%D0%B1%D0%B5%D0%BA%D0%BE%D1%80-%D2%9B%D0%B8%D0%BB%D0%B8%D1%88), |\n| [繁體中文](https:\/\/git-scm.com\/book\/zh-tw\/v2\/Git-%E5%9F%BA%E7%A4%8E-%E5%BE%A9%E5%8E%9F), |\n\nTranslations started for\n\n|   |\n|---|\n| [Беларуская](https:\/\/git-scm.com\/book\/be\/v2\/Git-Basics-Undoing-Things), |\n| [Indonesian](https:\/\/git-scm.com\/book\/id\/v2\/Git-Basics-Undoing-Things), |\n| [Italiano](https:\/\/git-scm.com\/book\/it\/v2\/Git-Basics-Undoing-Things), |\n| [Bahasa Melayu](https:\/\/git-scm.com\/book\/ms\/v2\/Git-Basics-Undoing-Things), |\n| [Português (Portugal)](https:\/\/git-scm.com\/book\/pt-pt\/v2\/No%C3%A7%C3%B5es-B%C3%A1sicas-do-Git-Desfazer-Coisas). |\n***\nThe source of this book is [hosted on GitHub.](https:\/\/github.com\/progit\/progit2)  \n Patches, suggestions and comments are welcome.\n\n[Chapters ▾](https:\/\/git-scm.com\/book\/en\/v2\/Git-Basics-Undoing-Things)\n\n1. ## 1\\. [Getting Started](https:\/\/git-scm.com\/book\/en\/v2\/Getting-Started-About-Version-Control)\n   1. 1\\.1 [About Version Control](https:\/\/git-scm.com\/book\/en\/v2\/Getting-Started-About-Version-Control)\n   2. 1\\.2 [A Short History of Git](https:\/\/git-scm.com\/book\/en\/v2\/Getting-Started-A-Short-History-of-Git)\n   3. 1\\.3 [What is Git?](https:\/\/git-scm.com\/book\/en\/v2\/Getting-Started-What-is-Git%3F)\n   4. 1\\.4 [The Command Line](https:\/\/git-scm.com\/book\/en\/v2\/Getting-Started-The-Command-Line)\n   5. 1\\.5 [Installing Git](https:\/\/git-scm.com\/book\/en\/v2\/Getting-Started-Installing-Git)\n   6. 1\\.6 [First-Time Git Setup](https:\/\/git-scm.com\/book\/en\/v2\/Getting-Started-First-Time-Git-Setup)\n   7. 1\\.7 [Getting Help](https:\/\/git-scm.com\/book\/en\/v2\/Getting-Started-Getting-Help)\n   8. 1\\.8 [Summary](https:\/\/git-scm.com\/book\/en\/v2\/Getting-Started-Summary)\n2. ## 2\\. [Git Basics](https:\/\/git-scm.com\/book\/en\/v2\/Git-Basics-Getting-a-Git-Repository)\n   1. 2\\.1 [Getting a Git Repository](https:\/\/git-scm.com\/book\/en\/v2\/Git-Basics-Getting-a-Git-Repository)\n   2. 2\\.2 [Recording Changes to the Repository](https:\/\/git-scm.com\/book\/en\/v2\/Git-Basics-Recording-Changes-to-the-Repository)\n   3. 2\\.3 [Viewing the Commit History](https:\/\/git-scm.com\/book\/en\/v2\/Git-Basics-Viewing-the-Commit-History)\n   4. 2\\.4 [Undoing Things](https:\/\/git-scm.com\/book\/en\/v2\/Git-Basics-Undoing-Things)\n   5. 2\\.5 [Working with Remotes](https:\/\/git-scm.com\/book\/en\/v2\/Git-Basics-Working-with-Remotes)\n   6. 2\\.6 [Tagging](https:\/\/git-scm.com\/book\/en\/v2\/Git-Basics-Tagging)\n   7. 2\\.7 [Git Aliases](https:\/\/git-scm.com\/book\/en\/v2\/Git-Basics-Git-Aliases)\n   8. 2\\.8 [Summary](https:\/\/git-scm.com\/book\/en\/v2\/Git-Basics-Summary)\n3. ## 3\\. [Git Branching](https:\/\/git-scm.com\/book\/en\/v2\/Git-Branching-Branches-in-a-Nutshell)\n   1. 3\\.1 [Branches in a Nutshell](https:\/\/git-scm.com\/book\/en\/v2\/Git-Branching-Branches-in-a-Nutshell)\n   2. 3\\.2 [Basic Branching and Merging](https:\/\/git-scm.com\/book\/en\/v2\/Git-Branching-Basic-Branching-and-Merging)\n   3. 3\\.3 [Branch Management](https:\/\/git-scm.com\/book\/en\/v2\/Git-Branching-Branch-Management)\n   4. 3\\.4 [Branching Workflows](https:\/\/git-scm.com\/book\/en\/v2\/Git-Branching-Branching-Workflows)\n   5. 3\\.5 [Remote Branches](https:\/\/git-scm.com\/book\/en\/v2\/Git-Branching-Remote-Branches)\n   6. 3\\.6 [Rebasing](https:\/\/git-scm.com\/book\/en\/v2\/Git-Branching-Rebasing)\n   7. 3\\.7 [Summary](https:\/\/git-scm.com\/book\/en\/v2\/Git-Branching-Summary)\n4. ## 4\\. [Git on the Server](https:\/\/git-scm.com\/book\/en\/v2\/Git-on-the-Server-The-Protocols)\n   1. 4\\.1 [The Protocols](https:\/\/git-scm.com\/book\/en\/v2\/Git-on-the-Server-The-Protocols)\n   2. 4\\.2 [Getting Git on a Server](https:\/\/git-scm.com\/book\/en\/v2\/Git-on-the-Server-Getting-Git-on-a-Server)\n   3. 4\\.3 [Generating Your SSH Public Key](https:\/\/git-scm.com\/book\/en\/v2\/Git-on-the-Server-Generating-Your-SSH-Public-Key)\n   4. 4\\.4 [Setting Up the Server](https:\/\/git-scm.com\/book\/en\/v2\/Git-on-the-Server-Setting-Up-the-Server)\n   5. 4\\.5 [Git Daemon](https:\/\/git-scm.com\/book\/en\/v2\/Git-on-the-Server-Git-Daemon)\n   6. 4\\.6 [Smart HTTP](https:\/\/git-scm.com\/book\/en\/v2\/Git-on-the-Server-Smart-HTTP)\n   7. 4\\.7 [GitWeb](https:\/\/git-scm.com\/book\/en\/v2\/Git-on-the-Server-GitWeb)\n   8. 4\\.8 [GitLab](https:\/\/git-scm.com\/book\/en\/v2\/Git-on-the-Server-GitLab)\n   9. 4\\.9 [Third Party Hosted Options](https:\/\/git-scm.com\/book\/en\/v2\/Git-on-the-Server-Third-Party-Hosted-Options)\n   10. 4\\.10 [Summary](https:\/\/git-scm.com\/book\/en\/v2\/Git-on-the-Server-Summary)\n5. ## 5\\. [Distributed Git](https:\/\/git-scm.com\/book\/en\/v2\/Distributed-Git-Distributed-Workflows)\n   1. 5\\.1 [Distributed Workflows](https:\/\/git-scm.com\/book\/en\/v2\/Distributed-Git-Distributed-Workflows)\n   2. 5\\.2 [Contributing to a Project](https:\/\/git-scm.com\/book\/en\/v2\/Distributed-Git-Contributing-to-a-Project)\n   3. 5\\.3 [Maintaining a Project](https:\/\/git-scm.com\/book\/en\/v2\/Distributed-Git-Maintaining-a-Project)\n   4. 5\\.4 [Summary](https:\/\/git-scm.com\/book\/en\/v2\/Distributed-Git-Summary)\n\n1. ## 6\\. [GitHub](https:\/\/git-scm.com\/book\/en\/v2\/GitHub-Account-Setup-and-Configuration)\n   1. 6\\.1 [Account Setup and Configuration](https:\/\/git-scm.com\/book\/en\/v2\/GitHub-Account-Setup-and-Configuration)\n   2. 6\\.2 [Contributing to a Project](https:\/\/git-scm.com\/book\/en\/v2\/GitHub-Contributing-to-a-Project)\n   3. 6\\.3 [Maintaining a Project](https:\/\/git-scm.com\/book\/en\/v2\/GitHub-Maintaining-a-Project)\n   4. 6\\.4 [Managing an organization](https:\/\/git-scm.com\/book\/en\/v2\/GitHub-Managing-an-organization)\n   5. 6\\.5 [Scripting GitHub](https:\/\/git-scm.com\/book\/en\/v2\/GitHub-Scripting-GitHub)\n   6. 6\\.6 [Summary](https:\/\/git-scm.com\/book\/en\/v2\/GitHub-Summary)\n2. ## 7\\. [Git Tools](https:\/\/git-scm.com\/book\/en\/v2\/Git-Tools-Revision-Selection)\n   1. 7\\.1 [Revision Selection](https:\/\/git-scm.com\/book\/en\/v2\/Git-Tools-Revision-Selection)\n   2. 7\\.2 [Interactive Staging](https:\/\/git-scm.com\/book\/en\/v2\/Git-Tools-Interactive-Staging)\n   3. 7\\.3 [Stashing and Cleaning](https:\/\/git-scm.com\/book\/en\/v2\/Git-Tools-Stashing-and-Cleaning)\n   4. 7\\.4 [Signing Your Work](https:\/\/git-scm.com\/book\/en\/v2\/Git-Tools-Signing-Your-Work)\n   5. 7\\.5 [Searching](https:\/\/git-scm.com\/book\/en\/v2\/Git-Tools-Searching)\n   6. 7\\.6 [Rewriting History](https:\/\/git-scm.com\/book\/en\/v2\/Git-Tools-Rewriting-History)\n   7. 7\\.7 [Reset Demystified](https:\/\/git-scm.com\/book\/en\/v2\/Git-Tools-Reset-Demystified)\n   8. 7\\.8 [Advanced Merging](https:\/\/git-scm.com\/book\/en\/v2\/Git-Tools-Advanced-Merging)\n   9. 7\\.9 [Rerere](https:\/\/git-scm.com\/book\/en\/v2\/Git-Tools-Rerere)\n   10. 7\\.10 [Debugging with Git](https:\/\/git-scm.com\/book\/en\/v2\/Git-Tools-Debugging-with-Git)\n   11. 7\\.11 [Submodules](https:\/\/git-scm.com\/book\/en\/v2\/Git-Tools-Submodules)\n   12. 7\\.12 [Bundling](https:\/\/git-scm.com\/book\/en\/v2\/Git-Tools-Bundling)\n   13. 7\\.13 [Replace](https:\/\/git-scm.com\/book\/en\/v2\/Git-Tools-Replace)\n   14. 7\\.14 [Credential Storage](https:\/\/git-scm.com\/book\/en\/v2\/Git-Tools-Credential-Storage)\n   15. 7\\.15 [Summary](https:\/\/git-scm.com\/book\/en\/v2\/Git-Tools-Summary)\n3. ## 8\\. [Customizing Git](https:\/\/git-scm.com\/book\/en\/v2\/Customizing-Git-Git-Configuration)\n   1. 8\\.1 [Git Configuration](https:\/\/git-scm.com\/book\/en\/v2\/Customizing-Git-Git-Configuration)\n   2. 8\\.2 [Git Attributes](https:\/\/git-scm.com\/book\/en\/v2\/Customizing-Git-Git-Attributes)\n   3. 8\\.3 [Git Hooks](https:\/\/git-scm.com\/book\/en\/v2\/Customizing-Git-Git-Hooks)\n   4. 8\\.4 [An Example Git-Enforced Policy](https:\/\/git-scm.com\/book\/en\/v2\/Customizing-Git-An-Example-Git-Enforced-Policy)\n   5. 8\\.5 [Summary](https:\/\/git-scm.com\/book\/en\/v2\/Customizing-Git-Summary)\n4. ## 9\\. [Git and Other Systems](https:\/\/git-scm.com\/book\/en\/v2\/Git-and-Other-Systems-Git-as-a-Client)\n   1. 9\\.1 [Git as a Client](https:\/\/git-scm.com\/book\/en\/v2\/Git-and-Other-Systems-Git-as-a-Client)\n   2. 9\\.2 [Migrating to Git](https:\/\/git-scm.com\/book\/en\/v2\/Git-and-Other-Systems-Migrating-to-Git)\n   3. 9\\.3 [Summary](https:\/\/git-scm.com\/book\/en\/v2\/Git-and-Other-Systems-Summary)\n5. ## 10\\. [Git Internals](https:\/\/git-scm.com\/book\/en\/v2\/Git-Internals-Plumbing-and-Porcelain)\n   1. 10\\.1 [Plumbing and Porcelain](https:\/\/git-scm.com\/book\/en\/v2\/Git-Internals-Plumbing-and-Porcelain)\n   2. 10\\.2 [Git Objects](https:\/\/git-scm.com\/book\/en\/v2\/Git-Internals-Git-Objects)\n   3. 10\\.3 [Git References](https:\/\/git-scm.com\/book\/en\/v2\/Git-Internals-Git-References)\n   4. 10\\.4 [Packfiles](https:\/\/git-scm.com\/book\/en\/v2\/Git-Internals-Packfiles)\n   5. 10\\.5 [The Refspec](https:\/\/git-scm.com\/book\/en\/v2\/Git-Internals-The-Refspec)\n   6. 10\\.6 [Transfer Protocols](https:\/\/git-scm.com\/book\/en\/v2\/Git-Internals-Transfer-Protocols)\n   7. 10\\.7 [Maintenance and Data Recovery](https:\/\/git-scm.com\/book\/en\/v2\/Git-Internals-Maintenance-and-Data-Recovery)\n   8. 10\\.8 [Environment Variables](https:\/\/git-scm.com\/book\/en\/v2\/Git-Internals-Environment-Variables)\n   9. 10\\.9 [Summary](https:\/\/git-scm.com\/book\/en\/v2\/Git-Internals-Summary)\n\n1. ## A1. [Appendix A: Git in Other Environments](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-A:-Git-in-Other-Environments-Graphical-Interfaces)\n   1. A1.1 [Graphical Interfaces](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-A:-Git-in-Other-Environments-Graphical-Interfaces)\n   2. A1.2 [Git in Visual Studio](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-A:-Git-in-Other-Environments-Git-in-Visual-Studio)\n   3. A1.3 [Git in Visual Studio Code](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-A:-Git-in-Other-Environments-Git-in-Visual-Studio-Code)\n   4. A1.4 [Git in IntelliJ \/ PyCharm \/ WebStorm \/ PhpStorm \/ RubyMine](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-A:-Git-in-Other-Environments-Git-in-IntelliJ-\/-PyCharm-\/-WebStorm-\/-PhpStorm-\/-RubyMine)\n   5. A1.5 [Git in Sublime Text](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-A:-Git-in-Other-Environments-Git-in-Sublime-Text)\n   6. A1.6 [Git in Bash](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-A:-Git-in-Other-Environments-Git-in-Bash)\n   7. A1.7 [Git in Zsh](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-A:-Git-in-Other-Environments-Git-in-Zsh)\n   8. A1.8 [Git in PowerShell](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-A:-Git-in-Other-Environments-Git-in-PowerShell)\n   9. A1.9 [Summary](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-A:-Git-in-Other-Environments-Summary)\n2. ## A2. [Appendix B: Embedding Git in your Applications](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-B:-Embedding-Git-in-your-Applications-Command-line-Git)\n   1. A2.1 [Command-line Git](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-B:-Embedding-Git-in-your-Applications-Command-line-Git)\n   2. A2.2 [Libgit2](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-B:-Embedding-Git-in-your-Applications-Libgit2)\n   3. A2.3 [JGit](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-B:-Embedding-Git-in-your-Applications-JGit)\n   4. A2.4 [go-git](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-B:-Embedding-Git-in-your-Applications-go-git)\n   5. A2.5 [Dulwich](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-B:-Embedding-Git-in-your-Applications-Dulwich)\n3. ## A3. [Appendix C: Git Commands](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-C:-Git-Commands-Setup-and-Config)\n   1. A3.1 [Setup and Config](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-C:-Git-Commands-Setup-and-Config)\n   2. A3.2 [Getting and Creating Projects](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-C:-Git-Commands-Getting-and-Creating-Projects)\n   3. A3.3 [Basic Snapshotting](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-C:-Git-Commands-Basic-Snapshotting)\n   4. A3.4 [Branching and Merging](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-C:-Git-Commands-Branching-and-Merging)\n   5. A3.5 [Sharing and Updating Projects](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-C:-Git-Commands-Sharing-and-Updating-Projects)\n   6. A3.6 [Inspection and Comparison](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-C:-Git-Commands-Inspection-and-Comparison)\n   7. A3.7 [Debugging](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-C:-Git-Commands-Debugging)\n   8. A3.8 [Patching](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-C:-Git-Commands-Patching)\n   9. A3.9 [Email](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-C:-Git-Commands-Email)\n   10. A3.10 [External Systems](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-C:-Git-Commands-External-Systems)\n   11. A3.11 [Administration](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-C:-Git-Commands-Administration)\n   12. A3.12 [Plumbing Commands](https:\/\/git-scm.com\/book\/en\/v2\/Appendix-C:-Git-Commands-Plumbing-Commands)\n\n2nd Edition\n\n# 2\\.4 Git Basics - Undoing Things\n## Undoing Things\nAt any stage, you may want to undo something. Here, we’ll review a few basic tools for undoing changes that you’ve made. Be careful, because you can’t always undo some of these undos. This is one of the few areas in Git where you may lose some work if you do it wrong.\n\nOne of the common undos takes place when you commit too early and possibly forget to add some files, or you mess up your commit message. If you want to redo that commit, make the additional changes you forgot, stage them, and commit again using the `--amend` option:\n```\n$ git commit --amend\n```\nThis command takes your staging area and uses it for the commit. If you’ve made no changes since your last commit (for instance, you run this command immediately after your previous commit), then your snapshot will look exactly the same, and all you’ll change is your commit message.\n\nThe same commit-message editor fires up, but it already contains the message of your previous commit. You can edit the message the same as always, but it overwrites your previous commit.\n\nAs an example, if you commit and then realize you forgot to stage the changes in a file you wanted to add to this commit, you can do something like this:\n```\n$ git commit -m 'Initial commit'\n$ git add forgotten_file\n$ git commit --amend\n```\nYou end up with a single commit — the second commit replaces the results of the first.\n\n|   |   |\n|---|---|\n| Note | It’s important to understand that when you’re amending your last commit, you’re not so much fixing it as *replacing* it entirely with a new, improved commit that pushes the old commit out of the way and puts the new commit in its place. Effectively, it’s as if the previous commit never happened, and it won’t show up in your repository history. The obvious value to amending commits is to make minor improvements to your last commit, without cluttering your repository history with commit messages of the form, “Oops, forgot to add a file” or “Darn, fixing a typo in last commit”. |\n\n|   |   |\n|---|---|\n| Note | Only amend commits that are still local and have not been pushed somewhere. Amending previously pushed commits and force pushing the branch will cause problems for your collaborators. For more on what happens when you do this and how to recover if you’re on the receiving end read [The Perils of Rebasing](https:\/\/git-scm.com\/book\/en\/v2\/ch00\/_rebase_peril). |\n\n### Unstaging a Staged File\nThe next two sections demonstrate how to work with your staging area and working directory changes. The nice part is that the command you use to determine the state of those two areas also reminds you how to undo changes to them. For example, let’s say you’ve changed two files and want to commit them as two separate changes, but you accidentally type `git add *` and stage them both. How can you unstage one of the two? The `git status` command reminds you:\n```\n$ git add *\n$ git status\nOn branch master\nChanges to be committed:\n  (use \"git reset HEAD <file>...\" to unstage)\n\n    renamed:    README.md -> README\n    modified:   CONTRIBUTING.md\n```\nRight below the “Changes to be committed” text, it says use `git reset HEAD <file>…` to unstage. So, let’s use that advice to unstage the `CONTRIBUTING.md` file:\n```\n$ git reset HEAD CONTRIBUTING.md\nUnstaged changes after reset:\nM\tCONTRIBUTING.md\n$ git status\nOn branch master\nChanges to be committed:\n  (use \"git reset HEAD <file>...\" to unstage)\n\n    renamed:    README.md -> README\n\nChanges not staged for commit:\n  (use \"git add <file>...\" to update what will be committed)\n  (use \"git checkout -- <file>...\" to discard changes in working directory)\n\n    modified:   CONTRIBUTING.md\n```\nThe command is a bit strange, but it works. The `CONTRIBUTING.md` file is modified but once again unstaged.\n\n|   |   |\n|---|---|\n| Note | It’s true that `git reset` can be a dangerous command, especially if you provide the `--hard` flag. However, in the scenario described above, the file in your working directory is not touched, so it’s relatively safe. |\n\nFor now this magic invocation is all you need to know about the `git reset` command. We’ll go into much more detail about what `reset` does and how to master it to do really interesting things in [Reset Demystified](https:\/\/git-scm.com\/book\/en\/v2\/ch00\/_git_reset).\n\n### Unmodifying a Modified File\nWhat if you realize that you don’t want to keep your changes to the `CONTRIBUTING.md` file? How can you easily unmodify it — revert it back to what it looked like when you last committed (or initially cloned, or however you got it into your working directory)? Luckily, `git status` tells you how to do that, too. In the last example output, the unstaged area looks like this:\n```\nChanges not staged for commit:\n  (use \"git add <file>...\" to update what will be committed)\n  (use \"git checkout -- <file>...\" to discard changes in working directory)\n\n    modified:   CONTRIBUTING.md\n```\nIt tells you pretty explicitly how to discard the changes you’ve made. Let’s do what it says:\n```\n$ git checkout -- CONTRIBUTING.md\n$ git status\nOn branch master\nChanges to be committed:\n  (use \"git reset HEAD <file>...\" to unstage)\n\n    renamed:    README.md -> README\n```\nYou can see that the changes have been reverted.\n\n|   |   |\n|---|---|\n| Important | It’s important to understand that `git checkout -- <file>` is a dangerous command. Any local changes you made to that file are gone — Git just replaced that file with the last staged or committed version. Don’t ever use this command unless you absolutely know that you don’t want those unsaved local changes. |\n\nIf you would like to keep the changes you’ve made to that file but still need to get it out of the way for now, we’ll go over stashing and branching in [Git Branching](https:\/\/git-scm.com\/book\/en\/v2\/ch00\/ch03-git-branching); these are generally better ways to go.\n\nRemember, anything that is *committed* in Git can almost always be recovered. Even commits that were on branches that were deleted or commits that were overwritten with an `--amend` commit can be recovered (see [Data Recovery](https:\/\/git-scm.com\/book\/en\/v2\/ch00\/_data_recovery) for data recovery). However, anything you lose that was never committed is likely never to be seen again.\n\n### Undoing things with git restore\nGit version 2.23.0 introduced a new command: `git restore`. It’s basically an alternative to `git reset` which we just covered. From Git version 2.23.0 onwards, Git will use `git restore` instead of `git reset` for many undo operations.\n\nLet’s retrace our steps, and undo things with `git restore` instead of `git reset`.\n\n#### Unstaging a Staged File with git restore\nThe next two sections demonstrate how to work with your staging area and working directory changes with `git restore`. The nice part is that the command you use to determine the state of those two areas also reminds you how to undo changes to them. For example, let’s say you’ve changed two files and want to commit them as two separate changes, but you accidentally type `git add *` and stage them both. How can you unstage one of the two? The `git status` command reminds you:\n```\n$ git add *\n$ git status\nOn branch master\nChanges to be committed:\n  (use \"git restore --staged <file>...\" to unstage)\n\tmodified:   CONTRIBUTING.md\n\trenamed:    README.md -> README\n```\nRight below the “Changes to be committed” text, it says use `git restore --staged <file>…` to unstage. So, let’s use that advice to unstage the `CONTRIBUTING.md` file:\n```\n$ git restore --staged CONTRIBUTING.md\n$ git status\nOn branch master\nChanges to be committed:\n  (use \"git restore --staged <file>...\" to unstage)\n\trenamed:    README.md -> README\n\nChanges not staged for commit:\n  (use \"git add <file>...\" to update what will be committed)\n  (use \"git restore <file>...\" to discard changes in working directory)\n\tmodified:   CONTRIBUTING.md\n```\nThe `CONTRIBUTING.md` file is modified but once again unstaged.\n\n#### Unmodifying a Modified File with git restore\nWhat if you realize that you don’t want to keep your changes to the `CONTRIBUTING.md` file? How can you easily unmodify it — revert it back to what it looked like when you last committed (or initially cloned, or however you got it into your working directory)? Luckily, `git status` tells you how to do that, too. In the last example output, the unstaged area looks like this:\n```\nChanges not staged for commit:\n  (use \"git add <file>...\" to update what will be committed)\n  (use \"git restore <file>...\" to discard changes in working directory)\n\tmodified:   CONTRIBUTING.md\n```\nIt tells you pretty explicitly how to discard the changes you’ve made. Let’s do what it says:\n```\n$ git restore CONTRIBUTING.md\n$ git status\nOn branch master\nChanges to be committed:\n  (use \"git restore --staged <file>...\" to unstage)\n\trenamed:    README.md -> README\n```\n|   |   |\n|---|---|\n| Important | It’s important to understand that `git restore <file>` is a dangerous command. Any local changes you made to that file are gone — Git just replaced that file with the last staged or committed version. Don’t ever use this command unless you absolutely know that you don’t want those unsaved local changes. |\n\n[prev](https:\/\/git-scm.com\/book\/en\/v2\/Git-Basics-Viewing-the-Commit-History) \\| [next](https:\/\/git-scm.com\/book\/en\/v2\/Git-Basics-Working-with-Remotes)\n\n[About this site](https:\/\/git-scm.com\/site)  \n Patches, suggestions, and comments are welcome.\n\nGit is a member of [Software Freedom Conservancy](https:\/\/git-scm.com\/sfc)","attrs_readable_markdown":"At any stage, you may want to undo something. Here, we’ll review a few basic tools for undoing changes that you’ve made. Be careful, because you can’t always undo some of these undos. This is one of the few areas in Git where you may lose some work if you do it wrong.\n\nOne of the common undos takes place when you commit too early and possibly forget to add some files, or you mess up your commit message. If you want to redo that commit, make the additional changes you forgot, stage them, and commit again using the `--amend` option:\n```\n$ git commit --amend\n```\nThis command takes your staging area and uses it for the commit. If you’ve made no changes since your last commit (for instance, you run this command immediately after your previous commit), then your snapshot will look exactly the same, and all you’ll change is your commit message.\n\nThe same commit-message editor fires up, but it already contains the message of your previous commit. You can edit the message the same as always, but it overwrites your previous commit.\n\nAs an example, if you commit and then realize you forgot to stage the changes in a file you wanted to add to this commit, you can do something like this:\n```\n$ git commit -m 'Initial commit'\n$ git add forgotten_file\n$ git commit --amend\n```\nYou end up with a single commit — the second commit replaces the results of the first.\n\n|   |   |\n|---|---|\n| Note | It’s important to understand that when you’re amending your last commit, you’re not so much fixing it as *replacing* it entirely with a new, improved commit that pushes the old commit out of the way and puts the new commit in its place. Effectively, it’s as if the previous commit never happened, and it won’t show up in your repository history. The obvious value to amending commits is to make minor improvements to your last commit, without cluttering your repository history with commit messages of the form, “Oops, forgot to add a file” or “Darn, fixing a typo in last commit”. |\n\n|   |   |\n|---|---|\n| Note | Only amend commits that are still local and have not been pushed somewhere. Amending previously pushed commits and force pushing the branch will cause problems for your collaborators. For more on what happens when you do this and how to recover if you’re on the receiving end read [The Perils of Rebasing](https:\/\/git-scm.com\/book\/en\/v2\/ch00\/_rebase_peril). |\n\n### Unstaging a Staged File\nThe next two sections demonstrate how to work with your staging area and working directory changes. The nice part is that the command you use to determine the state of those two areas also reminds you how to undo changes to them. For example, let’s say you’ve changed two files and want to commit them as two separate changes, but you accidentally type `git add *` and stage them both. How can you unstage one of the two? The `git status` command reminds you:\n```\n$ git add *\n$ git status\nOn branch master\nChanges to be committed:\n  (use \"git reset HEAD <file>...\" to unstage)\n\n    renamed:    README.md -> README\n    modified:   CONTRIBUTING.md\n```\nRight below the “Changes to be committed” text, it says use `git reset HEAD <file>…` to unstage. So, let’s use that advice to unstage the `CONTRIBUTING.md` file:\n```\n$ git reset HEAD CONTRIBUTING.md\nUnstaged changes after reset:\nM\tCONTRIBUTING.md\n$ git status\nOn branch master\nChanges to be committed:\n  (use \"git reset HEAD <file>...\" to unstage)\n\n    renamed:    README.md -> README\n\nChanges not staged for commit:\n  (use \"git add <file>...\" to update what will be committed)\n  (use \"git checkout -- <file>...\" to discard changes in working directory)\n\n    modified:   CONTRIBUTING.md\n```\nThe command is a bit strange, but it works. The `CONTRIBUTING.md` file is modified but once again unstaged.\n\n|   |   |\n|---|---|\n| Note | It’s true that `git reset` can be a dangerous command, especially if you provide the `--hard` flag. However, in the scenario described above, the file in your working directory is not touched, so it’s relatively safe. |\n\nFor now this magic invocation is all you need to know about the `git reset` command. We’ll go into much more detail about what `reset` does and how to master it to do really interesting things in [Reset Demystified](https:\/\/git-scm.com\/book\/en\/v2\/ch00\/_git_reset).\n\n### Unmodifying a Modified File\nWhat if you realize that you don’t want to keep your changes to the `CONTRIBUTING.md` file? How can you easily unmodify it — revert it back to what it looked like when you last committed (or initially cloned, or however you got it into your working directory)? Luckily, `git status` tells you how to do that, too. In the last example output, the unstaged area looks like this:\n```\nChanges not staged for commit:\n  (use \"git add <file>...\" to update what will be committed)\n  (use \"git checkout -- <file>...\" to discard changes in working directory)\n\n    modified:   CONTRIBUTING.md\n```\nIt tells you pretty explicitly how to discard the changes you’ve made. Let’s do what it says:\n```\n$ git checkout -- CONTRIBUTING.md\n$ git status\nOn branch master\nChanges to be committed:\n  (use \"git reset HEAD <file>...\" to unstage)\n\n    renamed:    README.md -> README\n```\nYou can see that the changes have been reverted.\n\n|   |   |\n|---|---|\n| Important | It’s important to understand that `git checkout -- <file>` is a dangerous command. Any local changes you made to that file are gone — Git just replaced that file with the last staged or committed version. Don’t ever use this command unless you absolutely know that you don’t want those unsaved local changes. |\n\nIf you would like to keep the changes you’ve made to that file but still need to get it out of the way for now, we’ll go over stashing and branching in [Git Branching](https:\/\/git-scm.com\/book\/en\/v2\/ch00\/ch03-git-branching); these are generally better ways to go.\n\nRemember, anything that is *committed* in Git can almost always be recovered. Even commits that were on branches that were deleted or commits that were overwritten with an `--amend` commit can be recovered (see [Data Recovery](https:\/\/git-scm.com\/book\/en\/v2\/ch00\/_data_recovery) for data recovery). However, anything you lose that was never committed is likely never to be seen again.\n\n### Undoing things with git restore\nGit version 2.23.0 introduced a new command: `git restore`. It’s basically an alternative to `git reset` which we just covered. From Git version 2.23.0 onwards, Git will use `git restore` instead of `git reset` for many undo operations.\n\nLet’s retrace our steps, and undo things with `git restore` instead of `git reset`.\n\n#### Unstaging a Staged File with git restore\nThe next two sections demonstrate how to work with your staging area and working directory changes with `git restore`. The nice part is that the command you use to determine the state of those two areas also reminds you how to undo changes to them. For example, let’s say you’ve changed two files and want to commit them as two separate changes, but you accidentally type `git add *` and stage them both. How can you unstage one of the two? The `git status` command reminds you:\n```\n$ git add *\n$ git status\nOn branch master\nChanges to be committed:\n  (use \"git restore --staged <file>...\" to unstage)\n\tmodified:   CONTRIBUTING.md\n\trenamed:    README.md -> README\n```\nRight below the “Changes to be committed” text, it says use `git restore --staged <file>…` to unstage. So, let’s use that advice to unstage the `CONTRIBUTING.md` file:\n```\n$ git restore --staged CONTRIBUTING.md\n$ git status\nOn branch master\nChanges to be committed:\n  (use \"git restore --staged <file>...\" to unstage)\n\trenamed:    README.md -> README\n\nChanges not staged for commit:\n  (use \"git add <file>...\" to update what will be committed)\n  (use \"git restore <file>...\" to discard changes in working directory)\n\tmodified:   CONTRIBUTING.md\n```\nThe `CONTRIBUTING.md` file is modified but once again unstaged.\n\n#### Unmodifying a Modified File with git restore\nWhat if you realize that you don’t want to keep your changes to the `CONTRIBUTING.md` file? How can you easily unmodify it — revert it back to what it looked like when you last committed (or initially cloned, or however you got it into your working directory)? Luckily, `git status` tells you how to do that, too. In the last example output, the unstaged area looks like this:\n```\nChanges not staged for commit:\n  (use \"git add <file>...\" to update what will be committed)\n  (use \"git restore <file>...\" to discard changes in working directory)\n\tmodified:   CONTRIBUTING.md\n```\nIt tells you pretty explicitly how to discard the changes you’ve made. Let’s do what it says:\n```\n$ git restore CONTRIBUTING.md\n$ git status\nOn branch master\nChanges to be committed:\n  (use \"git restore --staged <file>...\" to unstage)\n\trenamed:    README.md -> README\n```\n|   |   |\n|---|---|\n| Important | It’s important to understand that `git restore <file>` is a dangerous command. Any local changes you made to that file are gone — Git just replaced that file with the last staged or committed version. Don’t ever use this command unless you absolutely know that you don’t want those unsaved local changes. |","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

4 hours ago

🤖

ROBOTS ALLOWED

Page Info Filters

Filter	Status	Condition	Details
HTTP status	PASS	`download_http_code = 200`	HTTP 200
Age cutoff	PASS	`download_stamp > now() - 6 MONTH`	0 months ago
History drop	PASS	`isNull(history_drop_reason)`	No drop reason
Spam/ban	PASS	`fh_dont_index != 1 AND ml_spam_score = 0`	ml_spam_score=0
Canonical	PASS	`meta_canonical IS NULL OR = '' OR = src_unparsed`	Not set

Page Details

Property	Value
URL	https://git-scm.com/book/en/v2/Git-Basics-Undoing-Things
Last Crawled	2026-04-06 11:50:29 (4 hours ago)
First Indexed	2014-10-28 00:37:13 (11 years ago)
HTTP Status Code	200
Meta Title	Git - Undoing Things
Meta Description	null
Meta Canonical	null
Boilerpipe Text	At any stage, you may want to undo something. Here, we’ll review a few basic tools for undoing changes that you’ve made. Be careful, because you can’t always undo some of these undos. This is one of the few areas in Git where you may lose some work if you do it wrong. One of the common undos takes place when you commit too early and possibly forget to add some files, or you mess up your commit message. If you want to redo that commit, make the additional changes you forgot, stage them, and commit again using the --amend option: $ git commit --amend This command takes your staging area and uses it for the commit. If you’ve made no changes since your last commit (for instance, you run this command immediately after your previous commit), then your snapshot will look exactly the same, and all you’ll change is your commit message. The same commit-message editor fires up, but it already contains the message of your previous commit. You can edit the message the same as always, but it overwrites your previous commit. As an example, if you commit and then realize you forgot to stage the changes in a file you wanted to add to this commit, you can do something like this: $ git commit -m 'Initial commit' $ git add forgotten_file $ git commit --amend You end up with a single commit — the second commit replaces the results of the first. Note It’s important to understand that when you’re amending your last commit, you’re not so much fixing it as replacing it entirely with a new, improved commit that pushes the old commit out of the way and puts the new commit in its place. Effectively, it’s as if the previous commit never happened, and it won’t show up in your repository history. The obvious value to amending commits is to make minor improvements to your last commit, without cluttering your repository history with commit messages of the form, “Oops, forgot to add a file” or “Darn, fixing a typo in last commit”. Note Only amend commits that are still local and have not been pushed somewhere. Amending previously pushed commits and force pushing the branch will cause problems for your collaborators. For more on what happens when you do this and how to recover if you’re on the receiving end read The Perils of Rebasing . Unstaging a Staged File The next two sections demonstrate how to work with your staging area and working directory changes. The nice part is that the command you use to determine the state of those two areas also reminds you how to undo changes to them. For example, let’s say you’ve changed two files and want to commit them as two separate changes, but you accidentally type git add * and stage them both. How can you unstage one of the two? The git status command reminds you: $ git add * $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README modified: CONTRIBUTING.md Right below the “Changes to be committed” text, it says use git reset HEAD <file>… to unstage. So, let’s use that advice to unstage the CONTRIBUTING.md file: $ git reset HEAD CONTRIBUTING.md Unstaged changes after reset: M CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md The command is a bit strange, but it works. The CONTRIBUTING.md file is modified but once again unstaged. Note It’s true that git reset can be a dangerous command, especially if you provide the --hard flag. However, in the scenario described above, the file in your working directory is not touched, so it’s relatively safe. For now this magic invocation is all you need to know about the git reset command. We’ll go into much more detail about what reset does and how to master it to do really interesting things in Reset Demystified . Unmodifying a Modified File What if you realize that you don’t want to keep your changes to the CONTRIBUTING.md file? How can you easily unmodify it — revert it back to what it looked like when you last committed (or initially cloned, or however you got it into your working directory)? Luckily, git status tells you how to do that, too. In the last example output, the unstaged area looks like this: Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md It tells you pretty explicitly how to discard the changes you’ve made. Let’s do what it says: $ git checkout -- CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README You can see that the changes have been reverted. Important It’s important to understand that git checkout -- <file> is a dangerous command. Any local changes you made to that file are gone — Git just replaced that file with the last staged or committed version. Don’t ever use this command unless you absolutely know that you don’t want those unsaved local changes. If you would like to keep the changes you’ve made to that file but still need to get it out of the way for now, we’ll go over stashing and branching in Git Branching ; these are generally better ways to go. Remember, anything that is committed in Git can almost always be recovered. Even commits that were on branches that were deleted or commits that were overwritten with an --amend commit can be recovered (see Data Recovery for data recovery). However, anything you lose that was never committed is likely never to be seen again. Undoing things with git restore Git version 2.23.0 introduced a new command: git restore . It’s basically an alternative to git reset which we just covered. From Git version 2.23.0 onwards, Git will use git restore instead of git reset for many undo operations. Let’s retrace our steps, and undo things with git restore instead of git reset . Unstaging a Staged File with git restore The next two sections demonstrate how to work with your staging area and working directory changes with git restore . The nice part is that the command you use to determine the state of those two areas also reminds you how to undo changes to them. For example, let’s say you’ve changed two files and want to commit them as two separate changes, but you accidentally type git add * and stage them both. How can you unstage one of the two? The git status command reminds you: $ git add * $ git status On branch master Changes to be committed: (use "git restore --staged <file>..." to unstage) modified: CONTRIBUTING.md renamed: README.md -> README Right below the “Changes to be committed” text, it says use git restore --staged <file>… to unstage. So, let’s use that advice to unstage the CONTRIBUTING.md file: $ git restore --staged CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git restore --staged <file>..." to unstage) renamed: README.md -> README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: CONTRIBUTING.md The CONTRIBUTING.md file is modified but once again unstaged. Unmodifying a Modified File with git restore What if you realize that you don’t want to keep your changes to the CONTRIBUTING.md file? How can you easily unmodify it — revert it back to what it looked like when you last committed (or initially cloned, or however you got it into your working directory)? Luckily, git status tells you how to do that, too. In the last example output, the unstaged area looks like this: Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: CONTRIBUTING.md It tells you pretty explicitly how to discard the changes you’ve made. Let’s do what it says: $ git restore CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git restore --staged <file>..." to unstage) renamed: README.md -> README Important It’s important to understand that git restore <file> is a dangerous command. Any local changes you made to that file are gone — Git just replaced that file with the last staged or committed version. Don’t ever use this command unless you absolutely know that you don’t want those unsaved local changes.
Markdown	[![Git](https://git-scm.com/images/logo@2x.png)](https://git-scm.com/) \--distributed-is-the-new-centralized ![](https://git-scm.com/images/dark-mode.svg) - [About](https://git-scm.com/about) - [Trademark](https://git-scm.com/about/trademark) - [Learn](https://git-scm.com/learn) - [Book](https://git-scm.com/book) - [Cheat Sheet](https://git-scm.com/cheat-sheet) - [Videos](https://git-scm.com/videos) - [External Links](https://git-scm.com/doc/ext) - [Tools](https://git-scm.com/tools) - [Command Line](https://git-scm.com/tools/command-line) - [GUIs](https://git-scm.com/tools/guis) - [Hosting](https://git-scm.com/tools/hosting) - [Reference](https://git-scm.com/docs) - [Install](https://git-scm.com/install/linux) - [Community](https://git-scm.com/community) * This book is available in [English](https://git-scm.com/book/en/v2/Git-Basics-Undoing-Things). Full translation available in \| \| \|---\| \| [azərbaycan dili](https://git-scm.com/book/az/v2/Git%E2%80%99in-%C6%8Fsaslar%C4%B1-L%C9%99%C4%9Fv-Edil%C9%99n-%C4%B0%C5%9Fl%C9%99r-Geri-qaytar%C4%B1lan), \| \| [български език](https://git-scm.com/book/bg/v2/%D0%9E%D1%81%D0%BD%D0%BE%D0%B2%D0%B8-%D0%BD%D0%B0-Git-%D0%92%D1%8A%D0%B7%D1%81%D1%82%D0%B0%D0%BD%D0%BE%D0%B2%D1%8F%D0%B2%D0%B0%D0%BD%D0%B5-%D0%BD%D0%B0-%D0%BD%D0%B0%D0%BF%D1%80%D0%B0%D0%B2%D0%B5%D0%BD%D0%B8-%D0%B4%D0%B5%D0%B9%D1%81%D1%82%D0%B2%D0%B8%D1%8F), \| \| [Deutsch](https://git-scm.com/book/de/v2/Git-Grundlagen-Ungewollte-%C3%84nderungen-r%C3%BCckg%C3%A4ngig-machen), \| \| [Español](https://git-scm.com/book/es/v2/Fundamentos-de-Git-Deshacer-Cosas), \| \| [فارسی](https://git-scm.com/book/fa/v2/%D9%85%D9%82%D8%AF%D9%85%D8%A7%D8%AA-%DA%AF%DB%8C%D8%AA-git-basics-chapter-%D8%A8%D8%A7%D8%B2%DA%AF%D8%B1%D8%AF%D8%A7%D9%86%D8%AF%D9%86-%D8%AA%D8%BA%DB%8C%DB%8C%D8%B1%D8%A7%D8%AA-Undoing-Things), \| \| [Français](https://git-scm.com/book/fr/v2/Les-bases-de-Git-Annuler-des-actions), \| \| [Ελληνικά](https://git-scm.com/book/gr/v2/%CE%A4%CE%B1-%CE%B8%CE%B5%CE%BC%CE%B5%CE%BB%CE%B9%CF%8E%CE%B4%CE%B7-%CF%83%CF%84%CE%BF%CE%B9%CF%87%CE%B5%CE%AF%CE%B1-%CF%84%CE%BF%CF%85-Git-%CE%91%CE%BD%CE%B1%CE%B9%CF%81%CE%AD%CF%83%CE%B5%CE%B9%CF%82-undoing), \| \| [日本語](https://git-scm.com/book/ja/v2/Git-%E3%81%AE%E5%9F%BA%E6%9C%AC-%E4%BD%9C%E6%A5%AD%E3%81%AE%E3%82%84%E3%82%8A%E7%9B%B4%E3%81%97), \| \| [한국어](https://git-scm.com/book/ko/v2/Git%EC%9D%98-%EA%B8%B0%EC%B4%88-%EB%90%98%EB%8F%8C%EB%A6%AC%EA%B8%B0), \| \| [Nederlands](https://git-scm.com/book/nl/v2/Git-Basics-Dingen-ongedaan-maken), \| \| [Русский](https://git-scm.com/book/ru/v2/%D0%9E%D1%81%D0%BD%D0%BE%D0%B2%D1%8B-Git-%D0%9E%D0%BF%D0%B5%D1%80%D0%B0%D1%86%D0%B8%D0%B8-%D0%BE%D1%82%D0%BC%D0%B5%D0%BD%D1%8B), \| \| [Slovenščina](https://git-scm.com/book/sl/v2/Osnove-Git-Razveljavljanje-stvari), \| \| [Српски](https://git-scm.com/book/sr/v2/%D0%9E%D1%81%D0%BD%D0%BE%D0%B2%D0%B5-%D0%BF%D1%80%D0%BE%D0%B3%D1%80%D0%B0%D0%BC%D0%B0-%D0%93%D0%B8%D1%82-%D0%9E%D0%BF%D0%BE%D0%B7%D0%B8%D0%B2), \| \| [Svenska](https://git-scm.com/book/sv/v2/Grunderna-i-Git-%C3%85ngra-saker), \| \| [Tagalog](https://git-scm.com/book/tl/v2/Mga-Pangunahing-Kaalaman-sa-Git-Pag-Undo-ng-mga-Bagay), \| \| [Türkçe](https://git-scm.com/book/tr/v2/Git-Temelleri-De%C4%9Fi%C5%9Fiklikleri-Geri-Alma). \| \| [Українська](https://git-scm.com/book/uk/v2/%D0%9E%D1%81%D0%BD%D0%BE%D0%B2%D0%B8-Git-%D0%A1%D0%BA%D0%B0%D1%81%D1%83%D0%B2%D0%B0%D0%BD%D0%BD%D1%8F-%D1%80%D0%B5%D1%87%D0%B5%D0%B9), \| \| [简体中文](https://git-scm.com/book/zh/v2/Git-%E5%9F%BA%E7%A1%80-%E6%92%A4%E6%B6%88%E6%93%8D%E4%BD%9C), \| Partial translations available in \| \| \|---\| \| [Čeština](https://git-scm.com/book/cs/v2/Z%C3%A1klady-pr%C3%A1ce-se-syst%C3%A9mem-Git-N%C3%A1vrat-do-p%C5%99edchoz%C3%ADho-stavu), \| \| [Македонски](https://git-scm.com/book/mk/v2/%D0%9E%D1%81%D0%BD%D0%BE%D0%B2%D0%B8%D1%82%D0%B5-%D0%BD%D0%B0-Git-%D0%9F%D0%BE%D0%BD%D0%B8%D1%88%D1%82%D1%83%D0%B2%D0%B0%D1%9A%D0%B5-%D0%BD%D0%B0-%D0%BD%D0%B5%D1%88%D1%82%D0%B0%D1%82%D0%B0), \| \| [Polski](https://git-scm.com/book/pl/v2/Podstawy-Gita-Cofanie-zmian), \| \| [Português (Brasil)](https://git-scm.com/book/pt-br/v2/Fundamentos-de-Git-Desfazendo-coisas), \| \| [Ўзбекча](https://git-scm.com/book/uz/v2/Git-%D0%B0%D1%81%D0%BE%D1%81%D0%BB%D0%B0%D1%80%D0%B8-%D0%8E%D0%B7%D0%B3%D0%B0%D1%80%D0%B8%D1%88%D0%BB%D0%B0%D1%80%D0%BD%D0%B8-%D0%B1%D0%B5%D0%BA%D0%BE%D1%80-%D2%9B%D0%B8%D0%BB%D0%B8%D1%88), \| \| [繁體中文](https://git-scm.com/book/zh-tw/v2/Git-%E5%9F%BA%E7%A4%8E-%E5%BE%A9%E5%8E%9F), \| Translations started for \| \| \|---\| \| [Беларуская](https://git-scm.com/book/be/v2/Git-Basics-Undoing-Things), \| \| [Indonesian](https://git-scm.com/book/id/v2/Git-Basics-Undoing-Things), \| \| [Italiano](https://git-scm.com/book/it/v2/Git-Basics-Undoing-Things), \| \| [Bahasa Melayu](https://git-scm.com/book/ms/v2/Git-Basics-Undoing-Things), \| \| [Português (Portugal)](https://git-scm.com/book/pt-pt/v2/No%C3%A7%C3%B5es-B%C3%A1sicas-do-Git-Desfazer-Coisas). \| * The source of this book is [hosted on GitHub.](https://github.com/progit/progit2) Patches, suggestions and comments are welcome. [Chapters ▾](https://git-scm.com/book/en/v2/Git-Basics-Undoing-Things) 1. ## 1\. [Getting Started](https://git-scm.com/book/en/v2/Getting-Started-About-Version-Control) 1. 1\.1 [About Version Control](https://git-scm.com/book/en/v2/Getting-Started-About-Version-Control) 2. 1\.2 [A Short History of Git](https://git-scm.com/book/en/v2/Getting-Started-A-Short-History-of-Git) 3. 1\.3 [What is Git?](https://git-scm.com/book/en/v2/Getting-Started-What-is-Git%3F) 4. 1\.4 [The Command Line](https://git-scm.com/book/en/v2/Getting-Started-The-Command-Line) 5. 1\.5 [Installing Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) 6. 1\.6 [First-Time Git Setup](https://git-scm.com/book/en/v2/Getting-Started-First-Time-Git-Setup) 7. 1\.7 [Getting Help](https://git-scm.com/book/en/v2/Getting-Started-Getting-Help) 8. 1\.8 [Summary](https://git-scm.com/book/en/v2/Getting-Started-Summary) 2. ## 2\. [Git Basics](https://git-scm.com/book/en/v2/Git-Basics-Getting-a-Git-Repository) 1. 2\.1 [Getting a Git Repository](https://git-scm.com/book/en/v2/Git-Basics-Getting-a-Git-Repository) 2. 2\.2 [Recording Changes to the Repository](https://git-scm.com/book/en/v2/Git-Basics-Recording-Changes-to-the-Repository) 3. 2\.3 [Viewing the Commit History](https://git-scm.com/book/en/v2/Git-Basics-Viewing-the-Commit-History) 4. 2\.4 [Undoing Things](https://git-scm.com/book/en/v2/Git-Basics-Undoing-Things) 5. 2\.5 [Working with Remotes](https://git-scm.com/book/en/v2/Git-Basics-Working-with-Remotes) 6. 2\.6 [Tagging](https://git-scm.com/book/en/v2/Git-Basics-Tagging) 7. 2\.7 [Git Aliases](https://git-scm.com/book/en/v2/Git-Basics-Git-Aliases) 8. 2\.8 [Summary](https://git-scm.com/book/en/v2/Git-Basics-Summary) 3. ## 3\. [Git Branching](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell) 1. 3\.1 [Branches in a Nutshell](https://git-scm.com/book/en/v2/Git-Branching-Branches-in-a-Nutshell) 2. 3\.2 [Basic Branching and Merging](https://git-scm.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging) 3. 3\.3 [Branch Management](https://git-scm.com/book/en/v2/Git-Branching-Branch-Management) 4. 3\.4 [Branching Workflows](https://git-scm.com/book/en/v2/Git-Branching-Branching-Workflows) 5. 3\.5 [Remote Branches](https://git-scm.com/book/en/v2/Git-Branching-Remote-Branches) 6. 3\.6 [Rebasing](https://git-scm.com/book/en/v2/Git-Branching-Rebasing) 7. 3\.7 [Summary](https://git-scm.com/book/en/v2/Git-Branching-Summary) 4. ## 4\. [Git on the Server](https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols) 1. 4\.1 [The Protocols](https://git-scm.com/book/en/v2/Git-on-the-Server-The-Protocols) 2. 4\.2 [Getting Git on a Server](https://git-scm.com/book/en/v2/Git-on-the-Server-Getting-Git-on-a-Server) 3. 4\.3 [Generating Your SSH Public Key](https://git-scm.com/book/en/v2/Git-on-the-Server-Generating-Your-SSH-Public-Key) 4. 4\.4 [Setting Up the Server](https://git-scm.com/book/en/v2/Git-on-the-Server-Setting-Up-the-Server) 5. 4\.5 [Git Daemon](https://git-scm.com/book/en/v2/Git-on-the-Server-Git-Daemon) 6. 4\.6 [Smart HTTP](https://git-scm.com/book/en/v2/Git-on-the-Server-Smart-HTTP) 7. 4\.7 [GitWeb](https://git-scm.com/book/en/v2/Git-on-the-Server-GitWeb) 8. 4\.8 [GitLab](https://git-scm.com/book/en/v2/Git-on-the-Server-GitLab) 9. 4\.9 [Third Party Hosted Options](https://git-scm.com/book/en/v2/Git-on-the-Server-Third-Party-Hosted-Options) 10. 4\.10 [Summary](https://git-scm.com/book/en/v2/Git-on-the-Server-Summary) 5. ## 5\. [Distributed Git](https://git-scm.com/book/en/v2/Distributed-Git-Distributed-Workflows) 1. 5\.1 [Distributed Workflows](https://git-scm.com/book/en/v2/Distributed-Git-Distributed-Workflows) 2. 5\.2 [Contributing to a Project](https://git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project) 3. 5\.3 [Maintaining a Project](https://git-scm.com/book/en/v2/Distributed-Git-Maintaining-a-Project) 4. 5\.4 [Summary](https://git-scm.com/book/en/v2/Distributed-Git-Summary) 1. ## 6\. [GitHub](https://git-scm.com/book/en/v2/GitHub-Account-Setup-and-Configuration) 1. 6\.1 [Account Setup and Configuration](https://git-scm.com/book/en/v2/GitHub-Account-Setup-and-Configuration) 2. 6\.2 [Contributing to a Project](https://git-scm.com/book/en/v2/GitHub-Contributing-to-a-Project) 3. 6\.3 [Maintaining a Project](https://git-scm.com/book/en/v2/GitHub-Maintaining-a-Project) 4. 6\.4 [Managing an organization](https://git-scm.com/book/en/v2/GitHub-Managing-an-organization) 5. 6\.5 [Scripting GitHub](https://git-scm.com/book/en/v2/GitHub-Scripting-GitHub) 6. 6\.6 [Summary](https://git-scm.com/book/en/v2/GitHub-Summary) 2. ## 7\. [Git Tools](https://git-scm.com/book/en/v2/Git-Tools-Revision-Selection) 1. 7\.1 [Revision Selection](https://git-scm.com/book/en/v2/Git-Tools-Revision-Selection) 2. 7\.2 [Interactive Staging](https://git-scm.com/book/en/v2/Git-Tools-Interactive-Staging) 3. 7\.3 [Stashing and Cleaning](https://git-scm.com/book/en/v2/Git-Tools-Stashing-and-Cleaning) 4. 7\.4 [Signing Your Work](https://git-scm.com/book/en/v2/Git-Tools-Signing-Your-Work) 5. 7\.5 [Searching](https://git-scm.com/book/en/v2/Git-Tools-Searching) 6. 7\.6 [Rewriting History](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History) 7. 7\.7 [Reset Demystified](https://git-scm.com/book/en/v2/Git-Tools-Reset-Demystified) 8. 7\.8 [Advanced Merging](https://git-scm.com/book/en/v2/Git-Tools-Advanced-Merging) 9. 7\.9 [Rerere](https://git-scm.com/book/en/v2/Git-Tools-Rerere) 10. 7\.10 [Debugging with Git](https://git-scm.com/book/en/v2/Git-Tools-Debugging-with-Git) 11. 7\.11 [Submodules](https://git-scm.com/book/en/v2/Git-Tools-Submodules) 12. 7\.12 [Bundling](https://git-scm.com/book/en/v2/Git-Tools-Bundling) 13. 7\.13 [Replace](https://git-scm.com/book/en/v2/Git-Tools-Replace) 14. 7\.14 [Credential Storage](https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage) 15. 7\.15 [Summary](https://git-scm.com/book/en/v2/Git-Tools-Summary) 3. ## 8\. [Customizing Git](https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration) 1. 8\.1 [Git Configuration](https://git-scm.com/book/en/v2/Customizing-Git-Git-Configuration) 2. 8\.2 [Git Attributes](https://git-scm.com/book/en/v2/Customizing-Git-Git-Attributes) 3. 8\.3 [Git Hooks](https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks) 4. 8\.4 [An Example Git-Enforced Policy](https://git-scm.com/book/en/v2/Customizing-Git-An-Example-Git-Enforced-Policy) 5. 8\.5 [Summary](https://git-scm.com/book/en/v2/Customizing-Git-Summary) 4. ## 9\. [Git and Other Systems](https://git-scm.com/book/en/v2/Git-and-Other-Systems-Git-as-a-Client) 1. 9\.1 [Git as a Client](https://git-scm.com/book/en/v2/Git-and-Other-Systems-Git-as-a-Client) 2. 9\.2 [Migrating to Git](https://git-scm.com/book/en/v2/Git-and-Other-Systems-Migrating-to-Git) 3. 9\.3 [Summary](https://git-scm.com/book/en/v2/Git-and-Other-Systems-Summary) 5. ## 10\. [Git Internals](https://git-scm.com/book/en/v2/Git-Internals-Plumbing-and-Porcelain) 1. 10\.1 [Plumbing and Porcelain](https://git-scm.com/book/en/v2/Git-Internals-Plumbing-and-Porcelain) 2. 10\.2 [Git Objects](https://git-scm.com/book/en/v2/Git-Internals-Git-Objects) 3. 10\.3 [Git References](https://git-scm.com/book/en/v2/Git-Internals-Git-References) 4. 10\.4 [Packfiles](https://git-scm.com/book/en/v2/Git-Internals-Packfiles) 5. 10\.5 [The Refspec](https://git-scm.com/book/en/v2/Git-Internals-The-Refspec) 6. 10\.6 [Transfer Protocols](https://git-scm.com/book/en/v2/Git-Internals-Transfer-Protocols) 7. 10\.7 [Maintenance and Data Recovery](https://git-scm.com/book/en/v2/Git-Internals-Maintenance-and-Data-Recovery) 8. 10\.8 [Environment Variables](https://git-scm.com/book/en/v2/Git-Internals-Environment-Variables) 9. 10\.9 [Summary](https://git-scm.com/book/en/v2/Git-Internals-Summary) 1. ## A1. [Appendix A: Git in Other Environments](https://git-scm.com/book/en/v2/Appendix-A:-Git-in-Other-Environments-Graphical-Interfaces) 1. A1.1 [Graphical Interfaces](https://git-scm.com/book/en/v2/Appendix-A:-Git-in-Other-Environments-Graphical-Interfaces) 2. A1.2 [Git in Visual Studio](https://git-scm.com/book/en/v2/Appendix-A:-Git-in-Other-Environments-Git-in-Visual-Studio) 3. A1.3 [Git in Visual Studio Code](https://git-scm.com/book/en/v2/Appendix-A:-Git-in-Other-Environments-Git-in-Visual-Studio-Code) 4. A1.4 [Git in IntelliJ / PyCharm / WebStorm / PhpStorm / RubyMine](https://git-scm.com/book/en/v2/Appendix-A:-Git-in-Other-Environments-Git-in-IntelliJ-/-PyCharm-/-WebStorm-/-PhpStorm-/-RubyMine) 5. A1.5 [Git in Sublime Text](https://git-scm.com/book/en/v2/Appendix-A:-Git-in-Other-Environments-Git-in-Sublime-Text) 6. A1.6 [Git in Bash](https://git-scm.com/book/en/v2/Appendix-A:-Git-in-Other-Environments-Git-in-Bash) 7. A1.7 [Git in Zsh](https://git-scm.com/book/en/v2/Appendix-A:-Git-in-Other-Environments-Git-in-Zsh) 8. A1.8 [Git in PowerShell](https://git-scm.com/book/en/v2/Appendix-A:-Git-in-Other-Environments-Git-in-PowerShell) 9. A1.9 [Summary](https://git-scm.com/book/en/v2/Appendix-A:-Git-in-Other-Environments-Summary) 2. ## A2. [Appendix B: Embedding Git in your Applications](https://git-scm.com/book/en/v2/Appendix-B:-Embedding-Git-in-your-Applications-Command-line-Git) 1. A2.1 [Command-line Git](https://git-scm.com/book/en/v2/Appendix-B:-Embedding-Git-in-your-Applications-Command-line-Git) 2. A2.2 [Libgit2](https://git-scm.com/book/en/v2/Appendix-B:-Embedding-Git-in-your-Applications-Libgit2) 3. A2.3 [JGit](https://git-scm.com/book/en/v2/Appendix-B:-Embedding-Git-in-your-Applications-JGit) 4. A2.4 [go-git](https://git-scm.com/book/en/v2/Appendix-B:-Embedding-Git-in-your-Applications-go-git) 5. A2.5 [Dulwich](https://git-scm.com/book/en/v2/Appendix-B:-Embedding-Git-in-your-Applications-Dulwich) 3. ## A3. [Appendix C: Git Commands](https://git-scm.com/book/en/v2/Appendix-C:-Git-Commands-Setup-and-Config) 1. A3.1 [Setup and Config](https://git-scm.com/book/en/v2/Appendix-C:-Git-Commands-Setup-and-Config) 2. A3.2 [Getting and Creating Projects](https://git-scm.com/book/en/v2/Appendix-C:-Git-Commands-Getting-and-Creating-Projects) 3. A3.3 [Basic Snapshotting](https://git-scm.com/book/en/v2/Appendix-C:-Git-Commands-Basic-Snapshotting) 4. A3.4 [Branching and Merging](https://git-scm.com/book/en/v2/Appendix-C:-Git-Commands-Branching-and-Merging) 5. A3.5 [Sharing and Updating Projects](https://git-scm.com/book/en/v2/Appendix-C:-Git-Commands-Sharing-and-Updating-Projects) 6. A3.6 [Inspection and Comparison](https://git-scm.com/book/en/v2/Appendix-C:-Git-Commands-Inspection-and-Comparison) 7. A3.7 [Debugging](https://git-scm.com/book/en/v2/Appendix-C:-Git-Commands-Debugging) 8. A3.8 [Patching](https://git-scm.com/book/en/v2/Appendix-C:-Git-Commands-Patching) 9. A3.9 [Email](https://git-scm.com/book/en/v2/Appendix-C:-Git-Commands-Email) 10. A3.10 [External Systems](https://git-scm.com/book/en/v2/Appendix-C:-Git-Commands-External-Systems) 11. A3.11 [Administration](https://git-scm.com/book/en/v2/Appendix-C:-Git-Commands-Administration) 12. A3.12 [Plumbing Commands](https://git-scm.com/book/en/v2/Appendix-C:-Git-Commands-Plumbing-Commands) 2nd Edition # 2\.4 Git Basics - Undoing Things ## Undoing Things At any stage, you may want to undo something. Here, we’ll review a few basic tools for undoing changes that you’ve made. Be careful, because you can’t always undo some of these undos. This is one of the few areas in Git where you may lose some work if you do it wrong. One of the common undos takes place when you commit too early and possibly forget to add some files, or you mess up your commit message. If you want to redo that commit, make the additional changes you forgot, stage them, and commit again using the `--amend` option: ``` $ git commit --amend ``` This command takes your staging area and uses it for the commit. If you’ve made no changes since your last commit (for instance, you run this command immediately after your previous commit), then your snapshot will look exactly the same, and all you’ll change is your commit message. The same commit-message editor fires up, but it already contains the message of your previous commit. You can edit the message the same as always, but it overwrites your previous commit. As an example, if you commit and then realize you forgot to stage the changes in a file you wanted to add to this commit, you can do something like this: ``` $ git commit -m 'Initial commit' $ git add forgotten_file $ git commit --amend ``` You end up with a single commit — the second commit replaces the results of the first. \| \| \| \|---\|---\| \| Note \| It’s important to understand that when you’re amending your last commit, you’re not so much fixing it as replacing it entirely with a new, improved commit that pushes the old commit out of the way and puts the new commit in its place. Effectively, it’s as if the previous commit never happened, and it won’t show up in your repository history. The obvious value to amending commits is to make minor improvements to your last commit, without cluttering your repository history with commit messages of the form, “Oops, forgot to add a file” or “Darn, fixing a typo in last commit”. \| \| \| \| \|---\|---\| \| Note \| Only amend commits that are still local and have not been pushed somewhere. Amending previously pushed commits and force pushing the branch will cause problems for your collaborators. For more on what happens when you do this and how to recover if you’re on the receiving end read [The Perils of Rebasing](https://git-scm.com/book/en/v2/ch00/_rebase_peril). \| ### Unstaging a Staged File The next two sections demonstrate how to work with your staging area and working directory changes. The nice part is that the command you use to determine the state of those two areas also reminds you how to undo changes to them. For example, let’s say you’ve changed two files and want to commit them as two separate changes, but you accidentally type `git add ` and stage them both. How can you unstage one of the two? The `git status` command reminds you: ``` $ git add $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README modified: CONTRIBUTING.md ``` Right below the “Changes to be committed” text, it says use `git reset HEAD <file>…` to unstage. So, let’s use that advice to unstage the `CONTRIBUTING.md` file: ``` $ git reset HEAD CONTRIBUTING.md Unstaged changes after reset: M CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md ``` The command is a bit strange, but it works. The `CONTRIBUTING.md` file is modified but once again unstaged. \| \| \| \|---\|---\| \| Note \| It’s true that `git reset` can be a dangerous command, especially if you provide the `--hard` flag. However, in the scenario described above, the file in your working directory is not touched, so it’s relatively safe. \| For now this magic invocation is all you need to know about the `git reset` command. We’ll go into much more detail about what `reset` does and how to master it to do really interesting things in [Reset Demystified](https://git-scm.com/book/en/v2/ch00/_git_reset). ### Unmodifying a Modified File What if you realize that you don’t want to keep your changes to the `CONTRIBUTING.md` file? How can you easily unmodify it — revert it back to what it looked like when you last committed (or initially cloned, or however you got it into your working directory)? Luckily, `git status` tells you how to do that, too. In the last example output, the unstaged area looks like this: ``` Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md ``` It tells you pretty explicitly how to discard the changes you’ve made. Let’s do what it says: ``` $ git checkout -- CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README ``` You can see that the changes have been reverted. \| \| \| \|---\|---\| \| Important \| It’s important to understand that `git checkout -- <file>` is a dangerous command. Any local changes you made to that file are gone — Git just replaced that file with the last staged or committed version. Don’t ever use this command unless you absolutely know that you don’t want those unsaved local changes. \| If you would like to keep the changes you’ve made to that file but still need to get it out of the way for now, we’ll go over stashing and branching in [Git Branching](https://git-scm.com/book/en/v2/ch00/ch03-git-branching); these are generally better ways to go. Remember, anything that is committed in Git can almost always be recovered. Even commits that were on branches that were deleted or commits that were overwritten with an `--amend` commit can be recovered (see [Data Recovery](https://git-scm.com/book/en/v2/ch00/_data_recovery) for data recovery). However, anything you lose that was never committed is likely never to be seen again. ### Undoing things with git restore Git version 2.23.0 introduced a new command: `git restore`. It’s basically an alternative to `git reset` which we just covered. From Git version 2.23.0 onwards, Git will use `git restore` instead of `git reset` for many undo operations. Let’s retrace our steps, and undo things with `git restore` instead of `git reset`. #### Unstaging a Staged File with git restore The next two sections demonstrate how to work with your staging area and working directory changes with `git restore`. The nice part is that the command you use to determine the state of those two areas also reminds you how to undo changes to them. For example, let’s say you’ve changed two files and want to commit them as two separate changes, but you accidentally type `git add ` and stage them both. How can you unstage one of the two? The `git status` command reminds you: ``` $ git add $ git status On branch master Changes to be committed: (use "git restore --staged <file>..." to unstage) modified: CONTRIBUTING.md renamed: README.md -> README ``` Right below the “Changes to be committed” text, it says use `git restore --staged <file>…` to unstage. So, let’s use that advice to unstage the `CONTRIBUTING.md` file: ``` $ git restore --staged CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git restore --staged <file>..." to unstage) renamed: README.md -> README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: CONTRIBUTING.md ``` The `CONTRIBUTING.md` file is modified but once again unstaged. #### Unmodifying a Modified File with git restore What if you realize that you don’t want to keep your changes to the `CONTRIBUTING.md` file? How can you easily unmodify it — revert it back to what it looked like when you last committed (or initially cloned, or however you got it into your working directory)? Luckily, `git status` tells you how to do that, too. In the last example output, the unstaged area looks like this: ``` Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: CONTRIBUTING.md ``` It tells you pretty explicitly how to discard the changes you’ve made. Let’s do what it says: ``` $ git restore CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git restore --staged <file>..." to unstage) renamed: README.md -> README ``` \| \| \| \|---\|---\| \| Important \| It’s important to understand that `git restore <file>` is a dangerous command. Any local changes you made to that file are gone — Git just replaced that file with the last staged or committed version. Don’t ever use this command unless you absolutely know that you don’t want those unsaved local changes. \| [prev](https://git-scm.com/book/en/v2/Git-Basics-Viewing-the-Commit-History) \\| [next](https://git-scm.com/book/en/v2/Git-Basics-Working-with-Remotes) [About this site](https://git-scm.com/site) Patches, suggestions, and comments are welcome. Git is a member of [Software Freedom Conservancy](https://git-scm.com/sfc)
Readable Markdown	At any stage, you may want to undo something. Here, we’ll review a few basic tools for undoing changes that you’ve made. Be careful, because you can’t always undo some of these undos. This is one of the few areas in Git where you may lose some work if you do it wrong. One of the common undos takes place when you commit too early and possibly forget to add some files, or you mess up your commit message. If you want to redo that commit, make the additional changes you forgot, stage them, and commit again using the `--amend` option: ``` $ git commit --amend ``` This command takes your staging area and uses it for the commit. If you’ve made no changes since your last commit (for instance, you run this command immediately after your previous commit), then your snapshot will look exactly the same, and all you’ll change is your commit message. The same commit-message editor fires up, but it already contains the message of your previous commit. You can edit the message the same as always, but it overwrites your previous commit. As an example, if you commit and then realize you forgot to stage the changes in a file you wanted to add to this commit, you can do something like this: ``` $ git commit -m 'Initial commit' $ git add forgotten_file $ git commit --amend ``` You end up with a single commit — the second commit replaces the results of the first. \| \| \| \|---\|---\| \| Note \| It’s important to understand that when you’re amending your last commit, you’re not so much fixing it as replacing it entirely with a new, improved commit that pushes the old commit out of the way and puts the new commit in its place. Effectively, it’s as if the previous commit never happened, and it won’t show up in your repository history. The obvious value to amending commits is to make minor improvements to your last commit, without cluttering your repository history with commit messages of the form, “Oops, forgot to add a file” or “Darn, fixing a typo in last commit”. \| \| \| \| \|---\|---\| \| Note \| Only amend commits that are still local and have not been pushed somewhere. Amending previously pushed commits and force pushing the branch will cause problems for your collaborators. For more on what happens when you do this and how to recover if you’re on the receiving end read [The Perils of Rebasing](https://git-scm.com/book/en/v2/ch00/_rebase_peril). \| ### Unstaging a Staged File The next two sections demonstrate how to work with your staging area and working directory changes. The nice part is that the command you use to determine the state of those two areas also reminds you how to undo changes to them. For example, let’s say you’ve changed two files and want to commit them as two separate changes, but you accidentally type `git add ` and stage them both. How can you unstage one of the two? The `git status` command reminds you: ``` $ git add $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README modified: CONTRIBUTING.md ``` Right below the “Changes to be committed” text, it says use `git reset HEAD <file>…` to unstage. So, let’s use that advice to unstage the `CONTRIBUTING.md` file: ``` $ git reset HEAD CONTRIBUTING.md Unstaged changes after reset: M CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md ``` The command is a bit strange, but it works. The `CONTRIBUTING.md` file is modified but once again unstaged. \| \| \| \|---\|---\| \| Note \| It’s true that `git reset` can be a dangerous command, especially if you provide the `--hard` flag. However, in the scenario described above, the file in your working directory is not touched, so it’s relatively safe. \| For now this magic invocation is all you need to know about the `git reset` command. We’ll go into much more detail about what `reset` does and how to master it to do really interesting things in [Reset Demystified](https://git-scm.com/book/en/v2/ch00/_git_reset). ### Unmodifying a Modified File What if you realize that you don’t want to keep your changes to the `CONTRIBUTING.md` file? How can you easily unmodify it — revert it back to what it looked like when you last committed (or initially cloned, or however you got it into your working directory)? Luckily, `git status` tells you how to do that, too. In the last example output, the unstaged area looks like this: ``` Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git checkout -- <file>..." to discard changes in working directory) modified: CONTRIBUTING.md ``` It tells you pretty explicitly how to discard the changes you’ve made. Let’s do what it says: ``` $ git checkout -- CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git reset HEAD <file>..." to unstage) renamed: README.md -> README ``` You can see that the changes have been reverted. \| \| \| \|---\|---\| \| Important \| It’s important to understand that `git checkout -- <file>` is a dangerous command. Any local changes you made to that file are gone — Git just replaced that file with the last staged or committed version. Don’t ever use this command unless you absolutely know that you don’t want those unsaved local changes. \| If you would like to keep the changes you’ve made to that file but still need to get it out of the way for now, we’ll go over stashing and branching in [Git Branching](https://git-scm.com/book/en/v2/ch00/ch03-git-branching); these are generally better ways to go. Remember, anything that is committed in Git can almost always be recovered. Even commits that were on branches that were deleted or commits that were overwritten with an `--amend` commit can be recovered (see [Data Recovery](https://git-scm.com/book/en/v2/ch00/_data_recovery) for data recovery). However, anything you lose that was never committed is likely never to be seen again. ### Undoing things with git restore Git version 2.23.0 introduced a new command: `git restore`. It’s basically an alternative to `git reset` which we just covered. From Git version 2.23.0 onwards, Git will use `git restore` instead of `git reset` for many undo operations. Let’s retrace our steps, and undo things with `git restore` instead of `git reset`. #### Unstaging a Staged File with git restore The next two sections demonstrate how to work with your staging area and working directory changes with `git restore`. The nice part is that the command you use to determine the state of those two areas also reminds you how to undo changes to them. For example, let’s say you’ve changed two files and want to commit them as two separate changes, but you accidentally type `git add ` and stage them both. How can you unstage one of the two? The `git status` command reminds you: ``` $ git add $ git status On branch master Changes to be committed: (use "git restore --staged <file>..." to unstage) modified: CONTRIBUTING.md renamed: README.md -> README ``` Right below the “Changes to be committed” text, it says use `git restore --staged <file>…` to unstage. So, let’s use that advice to unstage the `CONTRIBUTING.md` file: ``` $ git restore --staged CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git restore --staged <file>..." to unstage) renamed: README.md -> README Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: CONTRIBUTING.md ``` The `CONTRIBUTING.md` file is modified but once again unstaged. #### Unmodifying a Modified File with git restore What if you realize that you don’t want to keep your changes to the `CONTRIBUTING.md` file? How can you easily unmodify it — revert it back to what it looked like when you last committed (or initially cloned, or however you got it into your working directory)? Luckily, `git status` tells you how to do that, too. In the last example output, the unstaged area looks like this: ``` Changes not staged for commit: (use "git add <file>..." to update what will be committed) (use "git restore <file>..." to discard changes in working directory) modified: CONTRIBUTING.md ``` It tells you pretty explicitly how to discard the changes you’ve made. Let’s do what it says: ``` $ git restore CONTRIBUTING.md $ git status On branch master Changes to be committed: (use "git restore --staged <file>..." to unstage) renamed: README.md -> README ``` \| \| \| \|---\|---\| \| Important \| It’s important to understand that `git restore <file>` is a dangerous command. Any local changes you made to that file are gone — Git just replaced that file with the last staged or committed version. Don’t ever use this command unless you absolutely know that you don’t want those unsaved local changes. \|
Shard	54 (laksa)
Root Hash	7104038400628677254
Unparsed URL	com,git-scm!/book/en/v2/Git-Basics-Undoing-Things s443