🕷️ Crawler Inspector

URL Lookup

Direct Parameter Lookup

Raw Queries and Responses

1. Shard Calculation

Query:

Response:

Calculated Shard: 63 (from laksa002)

2. Crawled Status Check

Query:

curl -X POST \
  'http://laksa063.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.git-tower.com/learn/git/commands/git-checkout\')), getAhrefsUnparsedNoserviceFromURL(\'https://www.git-tower.com/learn/git/commands/git-checkout\'))) FORMAT JSONEachRow'

Response:

{"found_url":"https:\/\/www.git-tower.com\/learn\/git\/commands\/git-checkout","crawl_time":1775746430,"first_indexed_time":1561778122,"http_code":200,"src_unparsed":"com,git-tower!www,\/learn\/git\/commands\/git-checkout s443","src_root_hash":"2236478454510524063","history_drop_reason":null,"meta_title":"git checkout - Switching branches and restoring files | Learn Version Control with Git","meta_descriptions":["Learn how to use the 'git checkout' command to switch the currently active branch, create a new branch, or restore files."],"attrs_boilerpipe_text":"The \"checkout\" command can switch the currently active branch - but it can also be used to restore files.\nThe most common use case for \"checkout\" is when you want to\nswitch to a different branch\n, making it the new HEAD branch.\nAnother use case for \"checkout\" is when you want to\nrestore a historic version\nof a specific file. Thereby, you can reset single files to earlier revisions - while keeping the rest of the project untouched.\nImportant Options\n<branch-name>\nThe name of a local branch that you want to switch to.\nBy specifying the name of a local branch, you will switch to this branch and make it the current \"HEAD\" branch.\n-b <new-branch>\nCreates a new local branch and directly switches to it.\nThis can be used as a shortcut instead of the following two commands:\ngit branch &lt;new-branch-name&gt;\ngit checkout &lt;new-branch-name&gt;\n.\n-b <new-branch> --track <remote-branch>\nCreates a new local branch - and sets up an \"upstream\" configuration.\nThis way, the new local branch has a\ntracking relationship\nwith its remote counterpart. This allows you to more easily see when the two aren't in sync (i.e. when\nunpushed\ncommits in the local branch or\nunpulled\ncommits in the remote exist).\n<file-path> <commit-hash>\nRestores a historic revision of a given file.\nBy providing HEAD as the revision, you can restore the last committed version of a file - effectively undoing any local changes that happened since then. If you want to restore a\nspecific\nearlier revision you can provide that revision's SHA-1 hash.\n-f \/ --force\nForces the branch switch even if the working tree or index differs from HEAD.\nWhen switching branches, any local changes to tracked files are discarded.\nImportant:\n-f\ndoes NOT delete untracked files. If an untracked file in your working directory would be overwritten by a file from the target branch, Git will still block the checkout — even with\n-f\n. To handle untracked files, use\ngit clean -fd\nfirst, or\ngit stash --include-untracked\n.\n-p \/ --patch\nInteractively select hunks to discard from the working tree.\nInstead of reverting an entire file, you can choose which individual changes to undo and which to keep. This is the inverse of\ngit add -p\n: where\nadd -p\nlets you selectively stage changes,\ncheckout -p\nlets you selectively discard them.\nUsage Examples\nIn its simplest (and most common) form, only the name of an existing local branch is specified:\n$ git checkout other-branch\nThis will make the given branch the new HEAD branch. If, in one go, you also want to create a new local branch, you can use the \"-b\" parameter:\n$ git checkout -b new-branch\nBy using the \"--track\" parameter, you can use a\nremote branch\nas the basis for a new local branch; this will also set up a \"tracking relationship\" between the two:\n$ git checkout -b new-branch --track origin\/develop\nAnother use case for \"checkout\" is when you want to restore an old revision of a file:\n$ git checkout 8a7b201 index.html\nIf you specify \"HEAD\" as the revision, you will restore the last committed version of the file, effectively undoing any local changes that you current have in that file:\n$ git checkout HEAD index.html\nTo discard all local changes in tracked files and restore them to the last committed state:\n$ git checkout .\nOr equivalently, using the explicit syntax with a double dash:\n$ git checkout -- .\nThe double dash (\n--\n) separates command options from file paths. This is useful to avoid ambiguity — for example, if you have a branch and a file with the same name:\n$ git checkout -- myfile.txt     # restores the file\n$ git checkout myfile.txt        # could mean file OR branch\nNote:\ngit checkout .\nonly affects tracked files. Untracked (new) files are not removed. Use\ngit clean -fd\nto remove untracked files.\nSince Git 2.23,\ngit restore .\nis the recommended command for discarding changes, as it avoids the overloaded nature of\ngit checkout\n.\nTo force a branch switch and discard any uncommitted changes to tracked files:\n$ git checkout -f main\nIf untracked files conflict with files on the target branch, remove them first with\ngit clean -fd\nor save them with\ngit stash --include-untracked\n:\n$ git clean -fd && git checkout -f main\nTo interactively select which changes to discard from a file:\n$ git checkout -p index.html\nGit will show each changed hunk and ask whether you want to discard it. This gives you fine-grained control over which changes to undo.\nCommon confusion: git checkout -d\nThere is no\n-d\nflag for\ngit checkout\n. If you're looking to delete a branch, use\ngit branch -d\ninstead:\n$ git branch -d feature-branch    # deletes the local branch\n$ git branch -D feature-branch    # force-deletes (even if unmerged)\nTip\nQuick Checkout in Tower\nIn case you are using the\nTower Git client\n, using checkout becomes easy as pie. Simply double-click a branch in the sidebar to make it the new HEAD branch - or choose a branch from a list.\nLearn More\nCheck out the chapter\nChecking Out a Local Branch\nin our free online book\nFind the full command description in the\nGit documentation\nMore\nfrequently asked questions\nabout Git & version control","attrs_markdown":"[Skip to main content](https:\/\/www.git-tower.com\/learn\/git\/commands\/git-checkout#main-content)\n\n[Tower](https:\/\/www.git-tower.com\/)\n\nNavigation\n\n- [Features](https:\/\/www.git-tower.com\/features)\n  - [Undo Anything Just press Cmd+Z](https:\/\/www.git-tower.com\/features\/undo)\n  - [Drag and Drop Make the complex effortless](https:\/\/www.git-tower.com\/features\/drag-and-drop)\n  - [Integrations Use your favorite tools](https:\/\/www.git-tower.com\/features\/integrations)\n  - [Tower Workflows Branching Configurations](https:\/\/www.git-tower.com\/features\/workflows)\n  - [Stacked Pull Requests Supercharged workflows](https:\/\/www.git-tower.com\/features\/stacked-prs)\n  - [All Features](https:\/\/www.git-tower.com\/features\/all-features)\n  - [Release Notes](https:\/\/www.git-tower.com\/release-notes)\n- [Pricing](https:\/\/www.git-tower.com\/pricing)\n- [Support](https:\/\/www.git-tower.com\/support)\n  - [Documentation](https:\/\/www.git-tower.com\/help)\n  - [Contact Us](https:\/\/www.git-tower.com\/support\/contact)\n  - [Account Login](https:\/\/account.git-tower.com\/)\n- [Learn Git](https:\/\/www.git-tower.com\/learn)\n  - [Video Course 24 episodes](https:\/\/www.git-tower.com\/learn\/git\/videos)\n  - [Online Book From novice to master](https:\/\/www.git-tower.com\/learn\/git\/ebook)\n  - [Cheat Sheets For quick lookup](https:\/\/www.git-tower.com\/learn\/cheat-sheets)\n  - [Webinar Learn from a Git professional](https:\/\/www.git-tower.com\/learn\/git\/webinar)\n  - [First Aid Kit Recover from mistakes](https:\/\/www.git-tower.com\/learn\/git\/first-aid-kit)\n  - [Advanced Git Kit Dive deeper](https:\/\/www.git-tower.com\/learn\/git\/advanced-git-kit)\n- [Blog](https:\/\/www.git-tower.com\/blog)\n- [Download](https:\/\/www.git-tower.com\/download\/mac)   [Download](https:\/\/www.git-tower.com\/download\/windows)\n\nGit Commands\n\nAn overview of the most important Git commands\n\n![Git Commands featured image](https:\/\/www.git-tower.com\/learn\/assets\/img\/header-visuals\/learners-questions.1773771024.svg)\n\n# git checkout\n**The \"checkout\" command can switch the currently active branch - but it can also be used to restore files.**\n\nThe most common use case for \"checkout\" is when you want to *switch to a different branch*, making it the new HEAD branch.\n\nAnother use case for \"checkout\" is when you want to *restore a historic version* of a specific file. Thereby, you can reset single files to earlier revisions - while keeping the rest of the project untouched.\n\n## Important Options\n#### \\<branch-name\\>\n**The name of a local branch that you want to switch to.** By specifying the name of a local branch, you will switch to this branch and make it the current \"HEAD\" branch.\n\n#### \\-b \\<new-branch\\>\n**Creates a new local branch and directly switches to it.** This can be used as a shortcut instead of the following two commands:  \n `git branch &lt;new-branch-name&gt;`  \n `git checkout &lt;new-branch-name&gt;`.\n\n#### \\-b \\<new-branch\\> --track \\<remote-branch\\>\n**Creates a new local branch - and sets up an \"upstream\" configuration.** This way, the new local branch has a [tracking relationship](https:\/\/www.git-tower.com\/learn\/git\/faq\/track-remote-upstream-branch) with its remote counterpart. This allows you to more easily see when the two aren't in sync (i.e. when *unpushed* commits in the local branch or *unpulled* commits in the remote exist).\n\n#### \\<file-path\\> \\<commit-hash\\>\n**Restores a historic revision of a given file.** By providing HEAD as the revision, you can restore the last committed version of a file - effectively undoing any local changes that happened since then. If you want to restore a *specific* earlier revision you can provide that revision's SHA-1 hash.\n\n#### \\-f \/ --force\n**Forces the branch switch even if the working tree or index differs from HEAD.** When switching branches, any local changes to tracked files are discarded.\n\n**Important:** `-f` does NOT delete untracked files. If an untracked file in your working directory would be overwritten by a file from the target branch, Git will still block the checkout — even with `-f`. To handle untracked files, use `git clean -fd` first, or `git stash --include-untracked`.\n\n#### \\-p \/ --patch\n**Interactively select hunks to discard from the working tree.** Instead of reverting an entire file, you can choose which individual changes to undo and which to keep. This is the inverse of `git add -p`: where `add -p` lets you selectively stage changes, `checkout -p` lets you selectively discard them.\n\n## Usage Examples\nIn its simplest (and most common) form, only the name of an existing local branch is specified:\n```\n$ git checkout other-branch\n```\nThis will make the given branch the new HEAD branch. If, in one go, you also want to create a new local branch, you can use the \"-b\" parameter:\n```\n$ git checkout -b new-branch\n```\nBy using the \"--track\" parameter, you can use a *remote branch* as the basis for a new local branch; this will also set up a \"tracking relationship\" between the two:\n```\n$ git checkout -b new-branch --track origin\/develop\n```\nAnother use case for \"checkout\" is when you want to restore an old revision of a file:\n```\n$ git checkout 8a7b201 index.html\n```\nIf you specify \"HEAD\" as the revision, you will restore the last committed version of the file, effectively undoing any local changes that you current have in that file:\n```\n$ git checkout HEAD index.html\n```\nTo discard all local changes in tracked files and restore them to the last committed state:\n```\n$ git checkout .\n```\nOr equivalently, using the explicit syntax with a double dash:\n```\n$ git checkout -- .\n```\nThe double dash (`--`) separates command options from file paths. This is useful to avoid ambiguity — for example, if you have a branch and a file with the same name:\n```\n$ git checkout -- myfile.txt     # restores the file\n$ git checkout myfile.txt        # could mean file OR branch\n```\n**Note:** `git checkout .` only affects tracked files. Untracked (new) files are not removed. Use `git clean -fd` to remove untracked files.\n\nSince Git 2.23, `git restore .` is the recommended command for discarding changes, as it avoids the overloaded nature of `git checkout`.\n\nTo force a branch switch and discard any uncommitted changes to tracked files:\n```\n$ git checkout -f main\n```\nIf untracked files conflict with files on the target branch, remove them first with `git clean -fd` or save them with `git stash --include-untracked`:\n```\n$ git clean -fd && git checkout -f main\n```\nTo interactively select which changes to discard from a file:\n```\n$ git checkout -p index.html\n```\nGit will show each changed hunk and ask whether you want to discard it. This gives you fine-grained control over which changes to undo.\n\n**Common confusion: git checkout -d**\n\nThere is no `-d` flag for `git checkout`. If you're looking to delete a branch, use `git branch -d` instead:\n```\n$ git branch -d feature-branch    # deletes the local branch\n$ git branch -D feature-branch    # force-deletes (even if unmerged)\n```\n\n##### Tip\n#### Quick Checkout in Tower\nIn case you are using the [Tower Git client](https:\/\/www.git-tower.com\/?utm_source=learn-website&utm_campaign=git-commands&utm_medium=easy-in-tower&utm_content=git-checkout), using checkout becomes easy as pie. Simply double-click a branch in the sidebar to make it the new HEAD branch - or choose a branch from a list.\n## Learn More\n- Check out the chapter [Checking Out a Local Branch](https:\/\/www.git-tower.com\/learn\/git\/ebook\/en\/desktop-gui\/branching-merging\/checkout#start) in our free online book\n- Find the full command description in the [Git documentation](https:\/\/git-scm.com\/docs\/git-checkout)\n- More [frequently asked questions](https:\/\/www.git-tower.com\/learn\/git\/faq) about Git & version control\n\n## Get our popular **Git Cheat Sheet** for free\\!\nYou'll find the most important commands on the front and helpful best practice tips on the back. Over 100,000 developers have downloaded it to make Git a little bit easier.\n\n![Get our popular Git Cheat Sheet for free\\!](https:\/\/www.git-tower.com\/learn\/assets\/img\/popups\/cheat-sheet-illu-huge.svg)\n\n## About Us\nAs the makers of [Tower, the best Git client for Mac and Windows](https:\/\/www.git-tower.com\/?utm_source=learn-website&utm_medium=about-us&utm_campaign=learn-git), we help over 100,000 users in companies like Apple, Google, Amazon, Twitter, and Ebay get the most out of Git.\n\nJust like with Tower, our mission with this platform is to help people become better professionals.\n\nThat's why we provide our guides, videos, and cheat sheets (about version control with Git and lots of other topics) for free.\n\n[![Tower icon](https:\/\/www.git-tower.com\/learn\/assets\/img\/tower-icon.1773771024.svg)](https:\/\/www.git-tower.com\/?utm_source=learn-website&utm_medium=about-us&utm_campaign=learn-git)\n\nAbout\n\n- [About](https:\/\/www.git-tower.com\/company\/about)\n- [Blog](https:\/\/www.git-tower.com\/blog)\n- [Merch](https:\/\/stuff.git-tower.com\/)\n- [Tower Git Client](https:\/\/www.git-tower.com\/)\n\nGit & Version Control\n\n- [Online Book](https:\/\/www.git-tower.com\/learn\/git\/ebook)\n- [First Aid Kit](https:\/\/www.git-tower.com\/learn\/git\/first-aid-kit)\n- [Webinar](https:\/\/www.git-tower.com\/learn\/git\/webinar)\n- [Video Course](https:\/\/www.git-tower.com\/learn\/git\/videos)\n- [Advanced Git Kit](https:\/\/www.git-tower.com\/learn\/git\/advanced-git-kit)\n- [FAQ](https:\/\/www.git-tower.com\/learn\/git\/faq)\n- [Glossary](https:\/\/www.git-tower.com\/learn\/git\/glossary)\n- [Commands](https:\/\/www.git-tower.com\/learn\/git\/commands)\n\nCheat Sheets\n\n- [Command Line 101](https:\/\/www.git-tower.com\/learn\/cheat-sheets\/cli)\n- [Git](https:\/\/www.git-tower.com\/learn\/cheat-sheets\/git)\n- [Git for Subversion Users](https:\/\/www.git-tower.com\/learn\/cheat-sheets\/git-for-svn)\n- [HTML](https:\/\/www.git-tower.com\/learn\/cheat-sheets\/html)\n- [Hugo](https:\/\/www.git-tower.com\/learn\/cheat-sheets\/hugo)\n- [JavaScript](https:\/\/www.git-tower.com\/learn\/cheat-sheets\/javascript)\n- [Markdown](https:\/\/www.git-tower.com\/learn\/cheat-sheets\/markdown)\n- [PowerShell](https:\/\/www.git-tower.com\/learn\/cheat-sheets\/powershell)\n- [Regex](https:\/\/www.git-tower.com\/learn\/cheat-sheets\/regex)\n- [Ruby on Rails](https:\/\/www.git-tower.com\/learn\/cheat-sheets\/ruby-on-rails)\n- [Tower Git Client](https:\/\/www.git-tower.com\/learn\/cheat-sheets\/tower)\n- [Visual Studio Code](https:\/\/www.git-tower.com\/learn\/cheat-sheets\/vscode)\n- [Website Optimization](https:\/\/www.git-tower.com\/learn\/cheat-sheets\/website-optimization)\n- [Workflow of Version Control](https:\/\/www.git-tower.com\/learn\/cheat-sheets\/vcs-workflow)\n- [Working with Branches in Git](https:\/\/www.git-tower.com\/learn\/cheat-sheets\/git-branches)\n- [Xcode](https:\/\/www.git-tower.com\/learn\/cheat-sheets\/xcode)\n\n## Your trial is downloading…\nTry Tower \"Pro\" for 30 days without limitations\\!\n\n![Tower Icon](https:\/\/www.git-tower.com\/learn\/assets\/img\/icons\/downloads-modal-app-icon.1773771024.png) Tower\n\nClose\n## Updates, Courses & Content via Email\n\n## Thank you for subscribing\nPlease check your email to confirm\n\nClose\n\n## Want to win one of our awesome Tower shirts?  **Tell your friends about Tower\\!**\n[Share on Twitter](https:\/\/www.git-tower.com\/learn\/git\/commands\/git-checkout)\n\nWe'll pick 4 winners every month who share this tweet\\!  \n Follow [@gittower](https:\/\/x.com\/gittower) to be notified if you win\\!\n\n## Try Tower for Free\nSign up below and use Tower \"Pro\" for 30 days without limitations\\!\n\nClose\n\n[Imprint \/ Legal Notice](https:\/\/www.git-tower.com\/legal\/imprint) \\| [Privacy Policy](https:\/\/www.git-tower.com\/legal\/privacy-policy) \\| Privacy Settings\n\n© 2010-2026 [Tower](https:\/\/www.git-tower.com\/) - Mentioned product names and logos are property of their respective owners.","attrs_readable_markdown":"**The \"checkout\" command can switch the currently active branch - but it can also be used to restore files.**\n\nThe most common use case for \"checkout\" is when you want to *switch to a different branch*, making it the new HEAD branch.\n\nAnother use case for \"checkout\" is when you want to *restore a historic version* of a specific file. Thereby, you can reset single files to earlier revisions - while keeping the rest of the project untouched.\n\n## Important Options\n#### \\<branch-name\\>\n**The name of a local branch that you want to switch to.** By specifying the name of a local branch, you will switch to this branch and make it the current \"HEAD\" branch.\n\n#### \\-b \\<new-branch\\>\n**Creates a new local branch and directly switches to it.** This can be used as a shortcut instead of the following two commands:  \n `git branch &lt;new-branch-name&gt;`  \n `git checkout &lt;new-branch-name&gt;`.\n\n#### \\-b \\<new-branch\\> --track \\<remote-branch\\>\n**Creates a new local branch - and sets up an \"upstream\" configuration.** This way, the new local branch has a [tracking relationship](https:\/\/www.git-tower.com\/learn\/git\/faq\/track-remote-upstream-branch) with its remote counterpart. This allows you to more easily see when the two aren't in sync (i.e. when *unpushed* commits in the local branch or *unpulled* commits in the remote exist).\n\n#### \\<file-path\\> \\<commit-hash\\>\n**Restores a historic revision of a given file.** By providing HEAD as the revision, you can restore the last committed version of a file - effectively undoing any local changes that happened since then. If you want to restore a *specific* earlier revision you can provide that revision's SHA-1 hash.\n\n#### \\-f \/ --force\n**Forces the branch switch even if the working tree or index differs from HEAD.** When switching branches, any local changes to tracked files are discarded.\n\n**Important:** `-f` does NOT delete untracked files. If an untracked file in your working directory would be overwritten by a file from the target branch, Git will still block the checkout — even with `-f`. To handle untracked files, use `git clean -fd` first, or `git stash --include-untracked`.\n\n#### \\-p \/ --patch\n**Interactively select hunks to discard from the working tree.** Instead of reverting an entire file, you can choose which individual changes to undo and which to keep. This is the inverse of `git add -p`: where `add -p` lets you selectively stage changes, `checkout -p` lets you selectively discard them.\n\n## Usage Examples\nIn its simplest (and most common) form, only the name of an existing local branch is specified:\n```\n$ git checkout other-branch\n```\nThis will make the given branch the new HEAD branch. If, in one go, you also want to create a new local branch, you can use the \"-b\" parameter:\n```\n$ git checkout -b new-branch\n```\nBy using the \"--track\" parameter, you can use a *remote branch* as the basis for a new local branch; this will also set up a \"tracking relationship\" between the two:\n```\n$ git checkout -b new-branch --track origin\/develop\n```\nAnother use case for \"checkout\" is when you want to restore an old revision of a file:\n```\n$ git checkout 8a7b201 index.html\n```\nIf you specify \"HEAD\" as the revision, you will restore the last committed version of the file, effectively undoing any local changes that you current have in that file:\n```\n$ git checkout HEAD index.html\n```\nTo discard all local changes in tracked files and restore them to the last committed state:\n```\n$ git checkout .\n```\nOr equivalently, using the explicit syntax with a double dash:\n```\n$ git checkout -- .\n```\nThe double dash (`--`) separates command options from file paths. This is useful to avoid ambiguity — for example, if you have a branch and a file with the same name:\n```\n$ git checkout -- myfile.txt     # restores the file\n$ git checkout myfile.txt        # could mean file OR branch\n```\n**Note:** `git checkout .` only affects tracked files. Untracked (new) files are not removed. Use `git clean -fd` to remove untracked files.\n\nSince Git 2.23, `git restore .` is the recommended command for discarding changes, as it avoids the overloaded nature of `git checkout`.\n\nTo force a branch switch and discard any uncommitted changes to tracked files:\n```\n$ git checkout -f main\n```\nIf untracked files conflict with files on the target branch, remove them first with `git clean -fd` or save them with `git stash --include-untracked`:\n```\n$ git clean -fd && git checkout -f main\n```\nTo interactively select which changes to discard from a file:\n```\n$ git checkout -p index.html\n```\nGit will show each changed hunk and ask whether you want to discard it. This gives you fine-grained control over which changes to undo.\n\n**Common confusion: git checkout -d**\n\nThere is no `-d` flag for `git checkout`. If you're looking to delete a branch, use `git branch -d` instead:\n```\n$ git branch -d feature-branch    # deletes the local branch\n$ git branch -D feature-branch    # force-deletes (even if unmerged)\n```\n\n##### Tip\n#### Quick Checkout in Tower\nIn case you are using the [Tower Git client](https:\/\/www.git-tower.com\/?utm_source=learn-website&utm_campaign=git-commands&utm_medium=easy-in-tower&utm_content=git-checkout), using checkout becomes easy as pie. Simply double-click a branch in the sidebar to make it the new HEAD branch - or choose a branch from a list.\n## Learn More\n- Check out the chapter [Checking Out a Local Branch](https:\/\/www.git-tower.com\/learn\/git\/ebook\/en\/desktop-gui\/branching-merging\/checkout#start) in our free online book\n- Find the full command description in the [Git documentation](https:\/\/git-scm.com\/docs\/git-checkout)\n- More [frequently asked questions](https:\/\/www.git-tower.com\/learn\/git\/faq) about Git & version control","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 hour 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://www.git-tower.com/learn/git/commands/git-checkout
Last Crawled	2026-04-09 14:53:50 (1 hour ago)
First Indexed	2019-06-29 03:15:22 (6 years ago)
HTTP Status Code	200
Meta Title	git checkout - Switching branches and restoring files \| Learn Version Control with Git
Meta Description	Learn how to use the 'git checkout' command to switch the currently active branch, create a new branch, or restore files.
Meta Canonical	null
Boilerpipe Text	The "checkout" command can switch the currently active branch - but it can also be used to restore files. The most common use case for "checkout" is when you want to switch to a different branch , making it the new HEAD branch. Another use case for "checkout" is when you want to restore a historic version of a specific file. Thereby, you can reset single files to earlier revisions - while keeping the rest of the project untouched. Important Options <branch-name> The name of a local branch that you want to switch to. By specifying the name of a local branch, you will switch to this branch and make it the current "HEAD" branch. -b <new-branch> Creates a new local branch and directly switches to it. This can be used as a shortcut instead of the following two commands: git branch <new-branch-name> git checkout <new-branch-name> . -b <new-branch> --track <remote-branch> Creates a new local branch - and sets up an "upstream" configuration. This way, the new local branch has a tracking relationship with its remote counterpart. This allows you to more easily see when the two aren't in sync (i.e. when unpushed commits in the local branch or unpulled commits in the remote exist). <file-path> <commit-hash> Restores a historic revision of a given file. By providing HEAD as the revision, you can restore the last committed version of a file - effectively undoing any local changes that happened since then. If you want to restore a specific earlier revision you can provide that revision's SHA-1 hash. -f / --force Forces the branch switch even if the working tree or index differs from HEAD. When switching branches, any local changes to tracked files are discarded. Important: -f does NOT delete untracked files. If an untracked file in your working directory would be overwritten by a file from the target branch, Git will still block the checkout — even with -f . To handle untracked files, use git clean -fd first, or git stash --include-untracked . -p / --patch Interactively select hunks to discard from the working tree. Instead of reverting an entire file, you can choose which individual changes to undo and which to keep. This is the inverse of git add -p : where add -p lets you selectively stage changes, checkout -p lets you selectively discard them. Usage Examples In its simplest (and most common) form, only the name of an existing local branch is specified: $ git checkout other-branch This will make the given branch the new HEAD branch. If, in one go, you also want to create a new local branch, you can use the "-b" parameter: $ git checkout -b new-branch By using the "--track" parameter, you can use a remote branch as the basis for a new local branch; this will also set up a "tracking relationship" between the two: $ git checkout -b new-branch --track origin/develop Another use case for "checkout" is when you want to restore an old revision of a file: $ git checkout 8a7b201 index.html If you specify "HEAD" as the revision, you will restore the last committed version of the file, effectively undoing any local changes that you current have in that file: $ git checkout HEAD index.html To discard all local changes in tracked files and restore them to the last committed state: $ git checkout . Or equivalently, using the explicit syntax with a double dash: $ git checkout -- . The double dash ( -- ) separates command options from file paths. This is useful to avoid ambiguity — for example, if you have a branch and a file with the same name: $ git checkout -- myfile.txt # restores the file $ git checkout myfile.txt # could mean file OR branch Note: git checkout . only affects tracked files. Untracked (new) files are not removed. Use git clean -fd to remove untracked files. Since Git 2.23, git restore . is the recommended command for discarding changes, as it avoids the overloaded nature of git checkout . To force a branch switch and discard any uncommitted changes to tracked files: $ git checkout -f main If untracked files conflict with files on the target branch, remove them first with git clean -fd or save them with git stash --include-untracked : $ git clean -fd && git checkout -f main To interactively select which changes to discard from a file: $ git checkout -p index.html Git will show each changed hunk and ask whether you want to discard it. This gives you fine-grained control over which changes to undo. Common confusion: git checkout -d There is no -d flag for git checkout . If you're looking to delete a branch, use git branch -d instead: $ git branch -d feature-branch # deletes the local branch $ git branch -D feature-branch # force-deletes (even if unmerged) Tip Quick Checkout in Tower In case you are using the Tower Git client , using checkout becomes easy as pie. Simply double-click a branch in the sidebar to make it the new HEAD branch - or choose a branch from a list. Learn More Check out the chapter Checking Out a Local Branch in our free online book Find the full command description in the Git documentation More frequently asked questions about Git & version control
Markdown	[Skip to main content](https://www.git-tower.com/learn/git/commands/git-checkout#main-content) [Tower](https://www.git-tower.com/) Navigation - [Features](https://www.git-tower.com/features) - [Undo Anything Just press Cmd+Z](https://www.git-tower.com/features/undo) - [Drag and Drop Make the complex effortless](https://www.git-tower.com/features/drag-and-drop) - [Integrations Use your favorite tools](https://www.git-tower.com/features/integrations) - [Tower Workflows Branching Configurations](https://www.git-tower.com/features/workflows) - [Stacked Pull Requests Supercharged workflows](https://www.git-tower.com/features/stacked-prs) - [All Features](https://www.git-tower.com/features/all-features) - [Release Notes](https://www.git-tower.com/release-notes) - [Pricing](https://www.git-tower.com/pricing) - [Support](https://www.git-tower.com/support) - [Documentation](https://www.git-tower.com/help) - [Contact Us](https://www.git-tower.com/support/contact) - [Account Login](https://account.git-tower.com/) - [Learn Git](https://www.git-tower.com/learn) - [Video Course 24 episodes](https://www.git-tower.com/learn/git/videos) - [Online Book From novice to master](https://www.git-tower.com/learn/git/ebook) - [Cheat Sheets For quick lookup](https://www.git-tower.com/learn/cheat-sheets) - [Webinar Learn from a Git professional](https://www.git-tower.com/learn/git/webinar) - [First Aid Kit Recover from mistakes](https://www.git-tower.com/learn/git/first-aid-kit) - [Advanced Git Kit Dive deeper](https://www.git-tower.com/learn/git/advanced-git-kit) - [Blog](https://www.git-tower.com/blog) - [Download](https://www.git-tower.com/download/mac) [Download](https://www.git-tower.com/download/windows) Git Commands An overview of the most important Git commands ![Git Commands featured image](https://www.git-tower.com/learn/assets/img/header-visuals/learners-questions.1773771024.svg) # git checkout The "checkout" command can switch the currently active branch - but it can also be used to restore files. The most common use case for "checkout" is when you want to switch to a different branch, making it the new HEAD branch. Another use case for "checkout" is when you want to restore a historic version of a specific file. Thereby, you can reset single files to earlier revisions - while keeping the rest of the project untouched. ## Important Options #### \<branch-name\> The name of a local branch that you want to switch to. By specifying the name of a local branch, you will switch to this branch and make it the current "HEAD" branch. #### \-b \<new-branch\> Creates a new local branch and directly switches to it. This can be used as a shortcut instead of the following two commands: `git branch <new-branch-name>` `git checkout <new-branch-name>`. #### \-b \<new-branch\> --track \<remote-branch\> Creates a new local branch - and sets up an "upstream" configuration. This way, the new local branch has a [tracking relationship](https://www.git-tower.com/learn/git/faq/track-remote-upstream-branch) with its remote counterpart. This allows you to more easily see when the two aren't in sync (i.e. when unpushed commits in the local branch or unpulled commits in the remote exist). #### \<file-path\> \<commit-hash\> Restores a historic revision of a given file. By providing HEAD as the revision, you can restore the last committed version of a file - effectively undoing any local changes that happened since then. If you want to restore a specific earlier revision you can provide that revision's SHA-1 hash. #### \-f / --force Forces the branch switch even if the working tree or index differs from HEAD. When switching branches, any local changes to tracked files are discarded. Important: `-f` does NOT delete untracked files. If an untracked file in your working directory would be overwritten by a file from the target branch, Git will still block the checkout — even with `-f`. To handle untracked files, use `git clean -fd` first, or `git stash --include-untracked`. #### \-p / --patch Interactively select hunks to discard from the working tree. Instead of reverting an entire file, you can choose which individual changes to undo and which to keep. This is the inverse of `git add -p`: where `add -p` lets you selectively stage changes, `checkout -p` lets you selectively discard them. ## Usage Examples In its simplest (and most common) form, only the name of an existing local branch is specified: ``` $ git checkout other-branch ``` This will make the given branch the new HEAD branch. If, in one go, you also want to create a new local branch, you can use the "-b" parameter: ``` $ git checkout -b new-branch ``` By using the "--track" parameter, you can use a remote branch as the basis for a new local branch; this will also set up a "tracking relationship" between the two: ``` $ git checkout -b new-branch --track origin/develop ``` Another use case for "checkout" is when you want to restore an old revision of a file: ``` $ git checkout 8a7b201 index.html ``` If you specify "HEAD" as the revision, you will restore the last committed version of the file, effectively undoing any local changes that you current have in that file: ``` $ git checkout HEAD index.html ``` To discard all local changes in tracked files and restore them to the last committed state: ``` $ git checkout . ``` Or equivalently, using the explicit syntax with a double dash: ``` $ git checkout -- . ``` The double dash (`--`) separates command options from file paths. This is useful to avoid ambiguity — for example, if you have a branch and a file with the same name: ``` $ git checkout -- myfile.txt # restores the file $ git checkout myfile.txt # could mean file OR branch ``` Note: `git checkout .` only affects tracked files. Untracked (new) files are not removed. Use `git clean -fd` to remove untracked files. Since Git 2.23, `git restore .` is the recommended command for discarding changes, as it avoids the overloaded nature of `git checkout`. To force a branch switch and discard any uncommitted changes to tracked files: ``` $ git checkout -f main ``` If untracked files conflict with files on the target branch, remove them first with `git clean -fd` or save them with `git stash --include-untracked`: ``` $ git clean -fd && git checkout -f main ``` To interactively select which changes to discard from a file: ``` $ git checkout -p index.html ``` Git will show each changed hunk and ask whether you want to discard it. This gives you fine-grained control over which changes to undo. Common confusion: git checkout -d There is no `-d` flag for `git checkout`. If you're looking to delete a branch, use `git branch -d` instead: ``` $ git branch -d feature-branch # deletes the local branch $ git branch -D feature-branch # force-deletes (even if unmerged) ``` ##### Tip #### Quick Checkout in Tower In case you are using the [Tower Git client](https://www.git-tower.com/?utm_source=learn-website&utm_campaign=git-commands&utm_medium=easy-in-tower&utm_content=git-checkout), using checkout becomes easy as pie. Simply double-click a branch in the sidebar to make it the new HEAD branch - or choose a branch from a list. ## Learn More - Check out the chapter [Checking Out a Local Branch](https://www.git-tower.com/learn/git/ebook/en/desktop-gui/branching-merging/checkout#start) in our free online book - Find the full command description in the [Git documentation](https://git-scm.com/docs/git-checkout) - More [frequently asked questions](https://www.git-tower.com/learn/git/faq) about Git & version control ## Get our popular Git Cheat Sheet for free\! You'll find the most important commands on the front and helpful best practice tips on the back. Over 100,000 developers have downloaded it to make Git a little bit easier. ![Get our popular Git Cheat Sheet for free\!](https://www.git-tower.com/learn/assets/img/popups/cheat-sheet-illu-huge.svg) ## About Us As the makers of [Tower, the best Git client for Mac and Windows](https://www.git-tower.com/?utm_source=learn-website&utm_medium=about-us&utm_campaign=learn-git), we help over 100,000 users in companies like Apple, Google, Amazon, Twitter, and Ebay get the most out of Git. Just like with Tower, our mission with this platform is to help people become better professionals. That's why we provide our guides, videos, and cheat sheets (about version control with Git and lots of other topics) for free. [![Tower icon](https://www.git-tower.com/learn/assets/img/tower-icon.1773771024.svg)](https://www.git-tower.com/?utm_source=learn-website&utm_medium=about-us&utm_campaign=learn-git) About - [About](https://www.git-tower.com/company/about) - [Blog](https://www.git-tower.com/blog) - [Merch](https://stuff.git-tower.com/) - [Tower Git Client](https://www.git-tower.com/) Git & Version Control - [Online Book](https://www.git-tower.com/learn/git/ebook) - [First Aid Kit](https://www.git-tower.com/learn/git/first-aid-kit) - [Webinar](https://www.git-tower.com/learn/git/webinar) - [Video Course](https://www.git-tower.com/learn/git/videos) - [Advanced Git Kit](https://www.git-tower.com/learn/git/advanced-git-kit) - [FAQ](https://www.git-tower.com/learn/git/faq) - [Glossary](https://www.git-tower.com/learn/git/glossary) - [Commands](https://www.git-tower.com/learn/git/commands) Cheat Sheets - [Command Line 101](https://www.git-tower.com/learn/cheat-sheets/cli) - [Git](https://www.git-tower.com/learn/cheat-sheets/git) - [Git for Subversion Users](https://www.git-tower.com/learn/cheat-sheets/git-for-svn) - [HTML](https://www.git-tower.com/learn/cheat-sheets/html) - [Hugo](https://www.git-tower.com/learn/cheat-sheets/hugo) - [JavaScript](https://www.git-tower.com/learn/cheat-sheets/javascript) - [Markdown](https://www.git-tower.com/learn/cheat-sheets/markdown) - [PowerShell](https://www.git-tower.com/learn/cheat-sheets/powershell) - [Regex](https://www.git-tower.com/learn/cheat-sheets/regex) - [Ruby on Rails](https://www.git-tower.com/learn/cheat-sheets/ruby-on-rails) - [Tower Git Client](https://www.git-tower.com/learn/cheat-sheets/tower) - [Visual Studio Code](https://www.git-tower.com/learn/cheat-sheets/vscode) - [Website Optimization](https://www.git-tower.com/learn/cheat-sheets/website-optimization) - [Workflow of Version Control](https://www.git-tower.com/learn/cheat-sheets/vcs-workflow) - [Working with Branches in Git](https://www.git-tower.com/learn/cheat-sheets/git-branches) - [Xcode](https://www.git-tower.com/learn/cheat-sheets/xcode) ## Your trial is downloading… Try Tower "Pro" for 30 days without limitations\! ![Tower Icon](https://www.git-tower.com/learn/assets/img/icons/downloads-modal-app-icon.1773771024.png) Tower Close ## Updates, Courses & Content via Email ## Thank you for subscribing Please check your email to confirm Close ## Want to win one of our awesome Tower shirts? Tell your friends about Tower\! [Share on Twitter](https://www.git-tower.com/learn/git/commands/git-checkout) We'll pick 4 winners every month who share this tweet\! Follow [@gittower](https://x.com/gittower) to be notified if you win\! ## Try Tower for Free Sign up below and use Tower "Pro" for 30 days without limitations\! Close [Imprint / Legal Notice](https://www.git-tower.com/legal/imprint) \\| [Privacy Policy](https://www.git-tower.com/legal/privacy-policy) \\| Privacy Settings © 2010-2026 [Tower](https://www.git-tower.com/) - Mentioned product names and logos are property of their respective owners.
Readable Markdown	The "checkout" command can switch the currently active branch - but it can also be used to restore files. The most common use case for "checkout" is when you want to switch to a different branch, making it the new HEAD branch. Another use case for "checkout" is when you want to restore a historic version of a specific file. Thereby, you can reset single files to earlier revisions - while keeping the rest of the project untouched. ## Important Options #### \<branch-name\> The name of a local branch that you want to switch to. By specifying the name of a local branch, you will switch to this branch and make it the current "HEAD" branch. #### \-b \<new-branch\> Creates a new local branch and directly switches to it. This can be used as a shortcut instead of the following two commands: `git branch <new-branch-name>` `git checkout <new-branch-name>`. #### \-b \<new-branch\> --track \<remote-branch\> Creates a new local branch - and sets up an "upstream" configuration. This way, the new local branch has a [tracking relationship](https://www.git-tower.com/learn/git/faq/track-remote-upstream-branch) with its remote counterpart. This allows you to more easily see when the two aren't in sync (i.e. when unpushed commits in the local branch or unpulled commits in the remote exist). #### \<file-path\> \<commit-hash\> Restores a historic revision of a given file. By providing HEAD as the revision, you can restore the last committed version of a file - effectively undoing any local changes that happened since then. If you want to restore a specific earlier revision you can provide that revision's SHA-1 hash. #### \-f / --force Forces the branch switch even if the working tree or index differs from HEAD. When switching branches, any local changes to tracked files are discarded. Important: `-f` does NOT delete untracked files. If an untracked file in your working directory would be overwritten by a file from the target branch, Git will still block the checkout — even with `-f`. To handle untracked files, use `git clean -fd` first, or `git stash --include-untracked`. #### \-p / --patch Interactively select hunks to discard from the working tree. Instead of reverting an entire file, you can choose which individual changes to undo and which to keep. This is the inverse of `git add -p`: where `add -p` lets you selectively stage changes, `checkout -p` lets you selectively discard them. ## Usage Examples In its simplest (and most common) form, only the name of an existing local branch is specified: ``` $ git checkout other-branch ``` This will make the given branch the new HEAD branch. If, in one go, you also want to create a new local branch, you can use the "-b" parameter: ``` $ git checkout -b new-branch ``` By using the "--track" parameter, you can use a remote branch as the basis for a new local branch; this will also set up a "tracking relationship" between the two: ``` $ git checkout -b new-branch --track origin/develop ``` Another use case for "checkout" is when you want to restore an old revision of a file: ``` $ git checkout 8a7b201 index.html ``` If you specify "HEAD" as the revision, you will restore the last committed version of the file, effectively undoing any local changes that you current have in that file: ``` $ git checkout HEAD index.html ``` To discard all local changes in tracked files and restore them to the last committed state: ``` $ git checkout . ``` Or equivalently, using the explicit syntax with a double dash: ``` $ git checkout -- . ``` The double dash (`--`) separates command options from file paths. This is useful to avoid ambiguity — for example, if you have a branch and a file with the same name: ``` $ git checkout -- myfile.txt # restores the file $ git checkout myfile.txt # could mean file OR branch ``` Note: `git checkout .` only affects tracked files. Untracked (new) files are not removed. Use `git clean -fd` to remove untracked files. Since Git 2.23, `git restore .` is the recommended command for discarding changes, as it avoids the overloaded nature of `git checkout`. To force a branch switch and discard any uncommitted changes to tracked files: ``` $ git checkout -f main ``` If untracked files conflict with files on the target branch, remove them first with `git clean -fd` or save them with `git stash --include-untracked`: ``` $ git clean -fd && git checkout -f main ``` To interactively select which changes to discard from a file: ``` $ git checkout -p index.html ``` Git will show each changed hunk and ask whether you want to discard it. This gives you fine-grained control over which changes to undo. Common confusion: git checkout -d There is no `-d` flag for `git checkout`. If you're looking to delete a branch, use `git branch -d` instead: ``` $ git branch -d feature-branch # deletes the local branch $ git branch -D feature-branch # force-deletes (even if unmerged) ``` ##### Tip #### Quick Checkout in Tower In case you are using the [Tower Git client](https://www.git-tower.com/?utm_source=learn-website&utm_campaign=git-commands&utm_medium=easy-in-tower&utm_content=git-checkout), using checkout becomes easy as pie. Simply double-click a branch in the sidebar to make it the new HEAD branch - or choose a branch from a list. ## Learn More - Check out the chapter [Checking Out a Local Branch](https://www.git-tower.com/learn/git/ebook/en/desktop-gui/branching-merging/checkout#start) in our free online book - Find the full command description in the [Git documentation](https://git-scm.com/docs/git-checkout) - More [frequently asked questions](https://www.git-tower.com/learn/git/faq) about Git & version control
Shard	63 (laksa)
Root Hash	2236478454510524063
Unparsed URL	com,git-tower!www,/learn/git/commands/git-checkout s443