🕷️ Crawler Inspector

URL Lookup

Direct Parameter Lookup

Raw Queries and Responses

1. Shard Calculation

Query:

Response:

Calculated Shard: 44 (from laksa050)

2. Crawled Status Check

Query:

curl -X POST \
  'http://laksa044.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.atlassian.com/git/tutorials/using-branches/git-checkout\')), getAhrefsUnparsedNoserviceFromURL(\'https://www.atlassian.com/git/tutorials/using-branches/git-checkout\'))) FORMAT JSONEachRow'

Response:

{"found_url":"https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/git-checkout","crawl_time":1775013133,"first_indexed_time":1411224330,"http_code":200,"src_unparsed":"com,atlassian!www,\/git\/tutorials\/using-branches\/git-checkout s443","src_root_hash":"11161217235333269644","history_drop_reason":null,"meta_title":"Git Checkout | Atlassian Git Tutorial","meta_descriptions":["Git branching intro. Create, list, rename, delete branches with git branch. git checkout: select which line of development you want and navigate branches"],"attrs_boilerpipe_text":"This page is an examination of the\ngit checkout\ncommand. It will cover usage examples and edge cases. In Git terms, a \"checkout\" is the act of switching between different versions of a target entity. The\ngit checkout\ncommand operates upon three distinct entities: files, commits, and branches. In addition to the definition of \"checkout\" the phrase \"checking out\" is commonly used to imply the act of executing the\ngit checkout\ncommand. In the\nUndoing Changes\ntopic, we saw how\ngit checkout\ncan be used to view old commits. The focus for the majority of this document will be checkout operations on branches.\nChecking out branches is similar to checking out old commits and files in that the working directory is updated to match the selected branch\/revision; however, new changes are saved in the project history—that is, it’s not a read-only operation.\nChecking out branches\nThe\ngit checkout\ncommand lets you navigate between the branches created by\ngit branch\n. Checking out a branch updates the files in the working directory to match the version stored in that branch, and it tells Git to record all new commits on that branch. Think of it as a way to select which line of development you’re working on.\nHaving a dedicated branch for each new feature is a dramatic shift from a traditional SVN workflow. It makes it ridiculously easy to try new experiments without the fear of destroying existing functionality, and it makes it possible to work on many unrelated features at the same time. In addition, branches also facilitate several collaborative workflows.\nThe\ngit checkout\ncommand may occasionally be confused with\ngit clone\n. The difference between the two commands is that clone works to fetch code from a remote repository, alternatively checkout works to switch between versions of code already on the local system.\nUsage: Existing branches\nAssuming the repo you're working in contains pre-existing branches, you can switch between these branches using\ngit checkout\n. To find out what branches are available and what the current branch name is, execute\ngit branch\n.\n$＞ git branch\nmain\nanother_branch\nfeature_inprogress_branch\n$＞ git checkout feature_inprogress_branch\nThe above example demonstrates how to view a list of available branches by executing the\ngit branch\ncommand, and switch to a specified branch, in this case, the\nfeature_inprogress_branch\n.\nNew branches\nGit checkout\nworks hand-in-hand with\ngit branch\n. The\ngit branch\ncommand can be used to create a new branch. When you want to start a new feature, you create a new branch off\nmain\n using\ngit branch new_branch\n. Once created you can then use\ngit checkout new_branch\nto switch to that branch. Additionally, The\ngit checkout\ncommand accepts a\n-b\nargument that acts as a convenience method which will create the new branch and immediately switch to it. You can work on multiple features in a single repository by switching between them with\ngit checkout\n.\ngit checkout -b ＜new-branch＞\nThe above example simultaneously creates and checks out\n＜new-branch＞\n. The\n-b\noption is a convenience flag that tells Git to run\ngit branch <new-branch>\nbefore running\ngit checkout ＜new-branch＞\n.\ngit checkout -b ＜new-branch＞ ＜existing-branch＞\nBy default\ngit checkout -b\nwill base the\nnew-branch\noff the current\nHEAD\n. An optional additional branch parameter can be passed to\ngit checkout\n. In the above example,\n＜existing-branch＞\nis passed which then bases\nnew-branch\noff of\nexisting-branch\ninstead of the current\nHEAD\n.\nSwitching branches\nSwitching branches is a straightforward operation. Executing the following will point\nHEAD\nto the tip of\n＜branchname＞.\ngit checkout ＜branchname＞\nGit tracks a history of checkout operations in the reflog. You can execute\ngit reflog\nto view the history.\nGit checkout a remote branch\nWhen collaborating with a team it is common to utilize remote repositories. These repositories may be hosted and shared or they may be another colleague's local copy. Each remote repository will contain its own set of branches. In order to checkout a remote branch you have to first fetch the contents of the branch.\ngit fetch --all\nIn modern versions of Git, you can then checkout the remote branch like a local branch.\ngit checkout ＜remotebranch＞\nOlder versions of Git require the creation of a new branch based on the\nremote\n.\ngit checkout -b ＜remotebranch＞ origin\/＜remotebranch＞\nAdditionally you can checkout a new local branch and reset it to the remote branches last commit.\ngit checkout -b ＜branchname＞\ngit reset --hard origin\/＜branchname＞\nDetached HEADS\nNow that we’ve seen the three main uses of\ngit checkout\non branches, it's important to discuss the\n“detached HEAD”\nstate. Remember that the\nHEAD\nis Git’s way of referring to the current snapshot. Internally, the\ngit checkout\ncommand simply updates the\nHEAD\nto point to either the specified branch or commit. When it points to a branch, Git doesn't complain, but when you check out a commit, it switches into a\n“detached HEAD”\nstate.\nThis is a warning telling you that everything you’re doing is “detached” from the rest of your project’s development. If you were to start developing a feature while in a detached\nHEAD\nstate, there would be no branch allowing you to get back to it. When you inevitably check out another branch (e.g., to merge your feature in), there would be no way to reference your feature:\nThe point is, your development should always take place on a branch—never on a detached\nHEAD\n. This makes sure you always have a reference to your new commits. However, if you’re just looking at an old commit, it doesn’t really matter if you’re in a detached\nHEAD\nstate or not.\nSummary\nThis page focused on usage of the\ngit checkout\ncommand when changing branches. In summation,\ngit checkout\n, when used on branches, alters the target of the\nHEAD\nref. It can be used to create branches, switch branches, and checkout remote branches. The\ngit checkout\ncommand is an essential tool for standard Git operation. It is a counterpart to\ngit merge\n. The\ngit checkout\nand\ngit merge\ncommands are critical tools to enabling\ngit workflows\n.","attrs_markdown":"[Skip to content](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/git-checkout#content)\n\n- [Products](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/git-checkout)\n  Featured\n  \n  Developers\n  \n  Product Managers\n  \n  IT professionals\n  \n  Business Teams\n  \n  Leadership Teams\n  \n  [See all apps](https:\/\/www.atlassian.com\/software)\n  \n  - ## Featured apps\n    - [**Jira** Flexible project management](https:\/\/www.atlassian.com\/software\/jira)\n    - [**Confluence** Knowledge, all in one place](https:\/\/www.atlassian.com\/software\/confluence)\n    - [**Jira Service Management** Deliver service at high velocity](https:\/\/www.atlassian.com\/software\/jira\/service-management)\n    ## Atlassian Collections\n  - [Supercharge teamwork seamlessly JiraConfluenceLoom](https:\/\/www.atlassian.com\/collections\/teamwork)\n  - [Optimize strategy and outcomes confidently FocusTalentAlign](https:\/\/www.atlassian.com\/collections\/strategy)\n  - [Deliver service at high-velocity Jira Service ManagementCustomer Service ManagementAssets](https:\/\/www.atlassian.com\/collections\/service)\n  - [Ship high-quality software fast Rovo DevDXPipelinesBitbucketCompass](https:\/\/www.atlassian.com\/collections\/software)\n  \n  Powered by\n  \n  [Rovo AI-powered apps – driven by your team's knowledge.](https:\/\/www.atlassian.com\/software\/rovo)\n  \n  - [**Jira** Flexible project management](https:\/\/www.atlassian.com\/software\/jira)\n  - [**Bitbucket** Source code and CI\/CD](https:\/\/www.atlassian.com\/software\/bitbucket)\n  - [**Rovo Dev** Agentic AI for developers](https:\/\/www.atlassian.com\/software\/rovo-dev)\n  - [**Pipelines** Scalable CI\/CD automation](https:\/\/www.atlassian.com\/software\/bitbucket\/features\/pipelines)\n  - [**DX** Measure productivity and AI impact](https:\/\/www.atlassian.com\/collections\/software)\n  - [**Compass** Software catalog for teams](https:\/\/www.atlassian.com\/software\/compass)\n  - [Ship high-quality software fast Rovo DevDXPipelinesBitbucketCompass](https:\/\/www.atlassian.com\/collections\/software)\n  \n  [Rovo AI-powered apps – driven by your team's knowledge.](https:\/\/www.atlassian.com\/software\/rovo)\n  \n  - [**Jira Product Discovery** Capture & prioritize ideas](https:\/\/www.atlassian.com\/software\/jira\/product-discovery)\n  - [**Jira** Flexible project management](https:\/\/www.atlassian.com\/software\/jira)\n  - [**Confluence** Knowledge, all in one place](https:\/\/www.atlassian.com\/software\/confluence)\n  - [Supercharge teamwork seamlessly JiraConfluenceLoom](https:\/\/www.atlassian.com\/collections\/teamwork)\n  \n  [Rovo AI-powered apps – driven by your team's knowledge.](https:\/\/www.atlassian.com\/software\/rovo)\n  \n  - [**Jira Service Management** Deliver service at high velocity](https:\/\/www.atlassian.com\/software\/jira\/service-management)\n  - [**Guard** Enhanced cloud security](https:\/\/www.atlassian.com\/software\/guard)\n  \n  [Rovo AI-powered apps – driven by your team's knowledge.](https:\/\/www.atlassian.com\/software\/rovo)\n  \n  - [**Jira** Flexible project management](https:\/\/www.atlassian.com\/software\/jira)\n  - [**Confluence** Knowledge, all in one place](https:\/\/www.atlassian.com\/software\/confluence)\n  - [**Trello** Capture and organize your tasks](https:\/\/trello.com\/home)\n  - [**Loom** Quick, async video updates](https:\/\/www.atlassian.com\/software\/loom)\n  - [**Jira Service Management** Deliver service at high velocity](https:\/\/www.atlassian.com\/software\/jira\/service-management)\n  - [**Customer Service Management** Customer experiences reimagined](https:\/\/www.atlassian.com\/software\/customer-service-management)\n  - [Supercharge teamwork seamlessly JiraConfluenceLoom](https:\/\/www.atlassian.com\/collections\/teamwork)\n  \n  [Rovo AI-powered apps – driven by your team's knowledge.](https:\/\/www.atlassian.com\/software\/rovo)\n  \n  - [**Focus** Enterprise-scale strategic planning](https:\/\/www.atlassian.com\/software\/focus)\n  - [**Talent** Knowledge workforce planning](https:\/\/www.atlassian.com\/software\/talent)\n  - [**Align** Enterprise-wide work planning & value](https:\/\/www.atlassian.com\/software\/jira\/align)\n  - [Optimize strategy and outcomes confidently FocusTalentAlign](https:\/\/www.atlassian.com\/collections\/strategy)\n  \n  [Rovo AI-powered apps – driven by your team's knowledge.](https:\/\/www.atlassian.com\/software\/rovo)\n- [Solutions](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/git-checkout)\n  Solutions\n  \n  ## By Use Case\n  - [Team collaboration](https:\/\/www.atlassian.com\/collections\/teamwork)\n  - [Strategy and planning](https:\/\/www.atlassian.com\/collections\/strategy)\n  - [Service management](https:\/\/www.atlassian.com\/collections\/service)\n  - [Software development](https:\/\/www.atlassian.com\/collections\/software)\n  \n  ## By Team\n  - [Software](https:\/\/www.atlassian.com\/collections\/software)\n  - [Marketing](https:\/\/www.atlassian.com\/teams\/marketing)\n  - [IT](https:\/\/www.atlassian.com\/teams\/it)\n  - [Product](https:\/\/www.atlassian.com\/software\/jira\/product-discovery%20)\n  \n  ## By Size\n  - [Enterprise](https:\/\/www.atlassian.com\/enterprise)\n  - [Small Business](https:\/\/www.atlassian.com\/software\/small-business)\n  - [Startup](https:\/\/www.atlassian.com\/software\/startups)\n  - [Non-profit](https:\/\/www.atlassian.com\/teams\/nonprofits)\n  \n  ## By Industry\n  - [Retail](https:\/\/www.atlassian.com\/industries\/retail)\n  - [Telecommunications](https:\/\/www.atlassian.com\/industries\/telecom)\n  - [Professional Services](https:\/\/www.atlassian.com\/industries\/professional-services)\n  - [Government](https:\/\/www.atlassian.com\/government)\n  \n  [Rovo AI-powered apps – driven by your team's knowledge.](https:\/\/www.atlassian.com\/software\/rovo)\n- [Why Atlassian?](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/git-checkout)\n  - [System of Work NewAtlassian's blueprint for how teams work together](https:\/\/www.atlassian.com\/system-of-work)\n  - [MarketplaceConnect thousands of apps to your Atlassian products](https:\/\/marketplace.atlassian.com\/)\n  - [CustomersCase studies & stories powered by teamwork](https:\/\/www.atlassian.com\/customers)\n  - [FedRAMPCompliant solutions for the public sector](https:\/\/www.atlassian.com\/trust\/compliance\/resources\/fedramp)\n  - [ResilienceEnterprise-grade & highly performant infrastructure](https:\/\/www.atlassian.com\/trust\/resilience)\n  - [PlatformOur deeply integrated, reliable & secure platform](https:\/\/www.atlassian.com\/platform)\n  - [Trust centerEnsure your data's security, compliance & availability](https:\/\/www.atlassian.com\/trust)\n- [Resources](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/git-checkout)\n  - [Customer SupportAsk questions, report bugs & give us feedback](https:\/\/support.atlassian.com\/)\n  - [Find PartnersConsulting, training & product customization support](https:\/\/partnerdirectory.atlassian.com\/)\n  - [Atlassian AscendResources and support for your transformation](https:\/\/www.atlassian.com\/migration)\n  - [CommunityLearn, connect and grow with the Atlassian Community](https:\/\/community.atlassian.com\/)\n  \n  ## Support\n  ## Resources\n- [Enterprise](https:\/\/www.atlassian.com\/enterprise)\n- More +\n\nGet it free\n\nSign in\n\nSign in\n\n- Products\n- Featured\n- Developers\n- Product Managers\n- IT professionals\n- Business Teams\n- Leadership Teams\n\n- Solutions\n- Why Atlassian?\n- Resources\n- [Enterprise](https:\/\/www.atlassian.com\/enterprise)\n\n[Sign in](https:\/\/id.atlassian.com\/login?continue=https%3A%2F%2Fwww.atlassian.com%2Fgateway%2Fapi%2Fstart%2Fauthredirect)\n\n- ## Featured apps\n  - [Jira Flexible project management](https:\/\/www.atlassian.com\/software\/jira)\n  - [Confluence Knowledge, all in one place](https:\/\/www.atlassian.com\/software\/confluence)\n  - [Jira Service Management Deliver service at high velocity](https:\/\/www.atlassian.com\/software\/jira\/service-management)\n  ## Atlassian Collections\n- [Supercharge teamwork seamlessly JiraConfluenceLoom](https:\/\/www.atlassian.com\/collections\/teamwork)\n- [Optimize strategy and outcomes confidently FocusTalentAlign](https:\/\/www.atlassian.com\/collections\/strategy)\n- [Deliver service at high-velocity Jira Service ManagementCustomer Service ManagementAssets](https:\/\/www.atlassian.com\/collections\/service)\n- [Ship high-quality software fast Rovo DevDXPipelinesBitbucketCompass](https:\/\/www.atlassian.com\/collections\/software)\n\nPowered by\n\n[Rovo AI-powered apps – driven by your team's knowledge.](https:\/\/www.atlassian.com\/software\/rovo)\n\nDevelopers\n\n- [**Jira** Flexible project management](https:\/\/www.atlassian.com\/software\/jira)\n- [**Bitbucket** Source code and CI\/CD](https:\/\/www.atlassian.com\/software\/bitbucket)\n- [**Rovo Dev** Agentic AI for developers](https:\/\/www.atlassian.com\/software\/rovo-dev)\n- [**Pipelines** Scalable CI\/CD automation](https:\/\/www.atlassian.com\/software\/bitbucket\/features\/pipelines)\n- [**DX** Measure productivity and AI impact](https:\/\/www.atlassian.com\/collections\/software)\n- [**Compass** Software catalog for teams](https:\/\/www.atlassian.com\/software\/compass)\n- [Ship high-quality software fast Rovo DevDXPipelinesBitbucketCompass](https:\/\/www.atlassian.com\/collections\/software)\n\n[Rovo AI-powered apps – driven by your team's knowledge.](https:\/\/www.atlassian.com\/software\/rovo)\n\nProduct Managers\n\n- [**Jira Product Discovery** Capture & prioritize ideas](https:\/\/www.atlassian.com\/software\/jira\/product-discovery)\n- [**Jira** Flexible project management](https:\/\/www.atlassian.com\/software\/jira)\n- [**Confluence** Knowledge, all in one place](https:\/\/www.atlassian.com\/software\/confluence)\n- [Supercharge teamwork seamlessly JiraConfluenceLoom](https:\/\/www.atlassian.com\/collections\/teamwork)\n\n[Rovo AI-powered apps – driven by your team's knowledge.](https:\/\/www.atlassian.com\/software\/rovo)\n\nIT professionals\n\n- [**Jira Service Management** Deliver service at high velocity](https:\/\/www.atlassian.com\/software\/jira\/service-management)\n- [**Guard** Enhanced cloud security](https:\/\/www.atlassian.com\/software\/guard)\n\n[Rovo AI-powered apps – driven by your team's knowledge.](https:\/\/www.atlassian.com\/software\/rovo)\n\nBusiness Teams\n\n- [**Jira** Flexible project management](https:\/\/www.atlassian.com\/software\/jira)\n- [**Confluence** Knowledge, all in one place](https:\/\/www.atlassian.com\/software\/confluence)\n- [**Trello** Capture and organize your tasks](https:\/\/trello.com\/home)\n- [**Loom** Quick, async video updates](https:\/\/www.atlassian.com\/software\/loom)\n- [**Jira Service Management** Deliver service at high velocity](https:\/\/www.atlassian.com\/software\/jira\/service-management)\n- [**Customer Service Management** Customer experiences reimagined](https:\/\/www.atlassian.com\/software\/customer-service-management)\n- [Supercharge teamwork seamlessly JiraConfluenceLoom](https:\/\/www.atlassian.com\/collections\/teamwork)\n\n[Rovo AI-powered apps – driven by your team's knowledge.](https:\/\/www.atlassian.com\/software\/rovo)\n\nLeadership Teams\n\n- [**Focus** Enterprise-scale strategic planning](https:\/\/www.atlassian.com\/software\/focus)\n- [**Talent** Knowledge workforce planning](https:\/\/www.atlassian.com\/software\/talent)\n- [**Align** Enterprise-wide work planning & value](https:\/\/www.atlassian.com\/software\/jira\/align)\n- [Optimize strategy and outcomes confidently FocusTalentAlign](https:\/\/www.atlassian.com\/collections\/strategy)\n\n[Rovo AI-powered apps – driven by your team's knowledge.](https:\/\/www.atlassian.com\/software\/rovo)\n\nSolutions\n\n## By Use Case\n- [Team collaboration](https:\/\/www.atlassian.com\/collections\/teamwork)\n- [Strategy and planning](https:\/\/www.atlassian.com\/collections\/strategy)\n- [Service management](https:\/\/www.atlassian.com\/collections\/service)\n- [Software development](https:\/\/www.atlassian.com\/collections\/software)\n\n## By Team\n- [Software](https:\/\/www.atlassian.com\/collections\/software)\n- [Marketing](https:\/\/www.atlassian.com\/teams\/marketing)\n- [IT](https:\/\/www.atlassian.com\/teams\/it)\n- [Product](https:\/\/www.atlassian.com\/software\/jira\/product-discovery%20)\n\n## By Size\n- [Enterprise](https:\/\/www.atlassian.com\/enterprise)\n- [Small Business](https:\/\/www.atlassian.com\/software\/small-business)\n- [Startup](https:\/\/www.atlassian.com\/software\/startups)\n- [Non-profit](https:\/\/www.atlassian.com\/teams\/nonprofits)\n\n## By Industry\n- [Retail](https:\/\/www.atlassian.com\/industries\/retail)\n- [Telecommunications](https:\/\/www.atlassian.com\/industries\/telecom)\n- [Professional Services](https:\/\/www.atlassian.com\/industries\/professional-services)\n- [Government](https:\/\/www.atlassian.com\/government)\n\n[Rovo AI-powered apps – driven by your team's knowledge.](https:\/\/www.atlassian.com\/software\/rovo)\n\nWhy Atlassian\n\n[System of Work NewAtlassian's blueprint for how teams work together](https:\/\/www.atlassian.com\/system-of-work)\n\n[MarketplaceConnect thousands of apps to your Atlassian products](https:\/\/marketplace.atlassian.com\/)\n\n[CustomersCase studies & stories powered by teamwork](https:\/\/www.atlassian.com\/customers)\n\n[FedRAMPCompliant solutions for the public sector](https:\/\/www.atlassian.com\/trust\/compliance\/resources\/fedramp)\n\n[ResilienceEnterprise-grade & highly performant infrastructure](https:\/\/www.atlassian.com\/trust\/resilience)\n\n[PlatformOur deeply integrated, reliable & secure platform](https:\/\/www.atlassian.com\/platform)\n\n[Trust centerEnsure your data's security, compliance & availability](https:\/\/www.atlassian.com\/trust)\n\nResources\n\n[Customer SupportAsk questions, report bugs & give us feedback](https:\/\/support.atlassian.com\/)\n\n[Find PartnersConsulting, training & product customization support](https:\/\/partnerdirectory.atlassian.com\/)\n\n[Atlassian AscendResources and support for your transformation](https:\/\/www.atlassian.com\/migration)\n\n[CommunityLearn, connect and grow with the Atlassian Community](https:\/\/community.atlassian.com\/)\n\nSupport\n\n- [General Inquiries](https:\/\/www.atlassian.com\/company\/contact\/general-inquiries)\n- [Technical Support](https:\/\/support.atlassian.com\/contact\/)\n- [Product Advice](https:\/\/www.atlassian.com\/company\/contact\/product-evaluator-advice)\n- [Pricing and Billing](https:\/\/www.atlassian.com\/company\/contact\/purchasing-licensing)\n- [Partner Support](https:\/\/www.atlassian.com\/partners)\n- [Developer Support](https:\/\/developer.atlassian.com\/)\n- [Enterprise Support](https:\/\/www.atlassian.com\/enterprise\/services)\n- [Purchasing and Licensing](https:\/\/www.atlassian.com\/licensing\/purchase-licensing)\n\nResources\n\n- [Project Management](https:\/\/www.atlassian.com\/project-management)\n- [Project Collaboration](https:\/\/www.atlassian.com\/work-management\/project-collaboration)\n- [Agile](https:\/\/www.atlassian.com\/agile)\n- [Team Playbook](https:\/\/www.atlassian.com\/team-playbook)\n- [Atlassian Learning](https:\/\/community.atlassian.com\/learning)\n- [Product Documentation](https:\/\/confluence.atlassian.com\/display\/ALLDOC\/Atlassian+Documentation)\n- [Get Started](https:\/\/www.atlassian.com\/get-started)\n\n[Skip to content](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/git-checkout#content)\n\n- Products\n- Featured\n- Developers\n- Product Managers\n- IT professionals\n- Business Teams\n- Leadership Teams\n\n- Solutions\n- Why Atlassian?\n- Resources\n- [Enterprise](https:\/\/www.atlassian.com\/enterprise)\n\n[Sign in](https:\/\/id.atlassian.com\/login?continue=https%3A%2F%2Fwww.atlassian.com%2Fgateway%2Fapi%2Fstart%2Fauthredirect)\n\n- ## Featured apps\n  - [Jira Flexible project management](https:\/\/www.atlassian.com\/software\/jira)\n  - [Confluence Knowledge, all in one place](https:\/\/www.atlassian.com\/software\/confluence)\n  - [Jira Service Management Deliver service at high velocity](https:\/\/www.atlassian.com\/software\/jira\/service-management)\n  ## Atlassian Collections\n- [Supercharge teamwork seamlessly JiraConfluenceLoom](https:\/\/www.atlassian.com\/collections\/teamwork)\n- [Optimize strategy and outcomes confidently FocusTalentAlign](https:\/\/www.atlassian.com\/collections\/strategy)\n- [Deliver service at high-velocity Jira Service ManagementCustomer Service ManagementAssets](https:\/\/www.atlassian.com\/collections\/service)\n- [Ship high-quality software fast Rovo DevDXPipelinesBitbucketCompass](https:\/\/www.atlassian.com\/collections\/software)\n\nPowered by\n\n[Rovo AI-powered apps – driven by your team's knowledge.](https:\/\/www.atlassian.com\/software\/rovo)\n\nDevelopers\n\n- [**Jira** Flexible project management](https:\/\/www.atlassian.com\/software\/jira)\n- [**Bitbucket** Source code and CI\/CD](https:\/\/www.atlassian.com\/software\/bitbucket)\n- [**Rovo Dev** Agentic AI for developers](https:\/\/www.atlassian.com\/software\/rovo-dev)\n- [**Pipelines** Scalable CI\/CD automation](https:\/\/www.atlassian.com\/software\/bitbucket\/features\/pipelines)\n- [**DX** Measure productivity and AI impact](https:\/\/www.atlassian.com\/collections\/software)\n- [**Compass** Software catalog for teams](https:\/\/www.atlassian.com\/software\/compass)\n- [Ship high-quality software fast Rovo DevDXPipelinesBitbucketCompass](https:\/\/www.atlassian.com\/collections\/software)\n\n[Rovo AI-powered apps – driven by your team's knowledge.](https:\/\/www.atlassian.com\/software\/rovo)\n\nProduct Managers\n\n- [**Jira Product Discovery** Capture & prioritize ideas](https:\/\/www.atlassian.com\/software\/jira\/product-discovery)\n- [**Jira** Flexible project management](https:\/\/www.atlassian.com\/software\/jira)\n- [**Confluence** Knowledge, all in one place](https:\/\/www.atlassian.com\/software\/confluence)\n- [Supercharge teamwork seamlessly JiraConfluenceLoom](https:\/\/www.atlassian.com\/collections\/teamwork)\n\n[Rovo AI-powered apps – driven by your team's knowledge.](https:\/\/www.atlassian.com\/software\/rovo)\n\nIT professionals\n\n- [**Jira Service Management** Deliver service at high velocity](https:\/\/www.atlassian.com\/software\/jira\/service-management)\n- [**Guard** Enhanced cloud security](https:\/\/www.atlassian.com\/software\/guard)\n\n[Rovo AI-powered apps – driven by your team's knowledge.](https:\/\/www.atlassian.com\/software\/rovo)\n\nBusiness Teams\n\n- [**Jira** Flexible project management](https:\/\/www.atlassian.com\/software\/jira)\n- [**Confluence** Knowledge, all in one place](https:\/\/www.atlassian.com\/software\/confluence)\n- [**Trello** Capture and organize your tasks](https:\/\/trello.com\/home)\n- [**Loom** Quick, async video updates](https:\/\/www.atlassian.com\/software\/loom)\n- [**Jira Service Management** Deliver service at high velocity](https:\/\/www.atlassian.com\/software\/jira\/service-management)\n- [**Customer Service Management** Customer experiences reimagined](https:\/\/www.atlassian.com\/software\/customer-service-management)\n- [Supercharge teamwork seamlessly JiraConfluenceLoom](https:\/\/www.atlassian.com\/collections\/teamwork)\n\n[Rovo AI-powered apps – driven by your team's knowledge.](https:\/\/www.atlassian.com\/software\/rovo)\n\nLeadership Teams\n\n- [**Focus** Enterprise-scale strategic planning](https:\/\/www.atlassian.com\/software\/focus)\n- [**Talent** Knowledge workforce planning](https:\/\/www.atlassian.com\/software\/talent)\n- [**Align** Enterprise-wide work planning & value](https:\/\/www.atlassian.com\/software\/jira\/align)\n- [Optimize strategy and outcomes confidently FocusTalentAlign](https:\/\/www.atlassian.com\/collections\/strategy)\n\n[Rovo AI-powered apps – driven by your team's knowledge.](https:\/\/www.atlassian.com\/software\/rovo)\n\nSolutions\n\n## By Use Case\n- [Team collaboration](https:\/\/www.atlassian.com\/collections\/teamwork)\n- [Strategy and planning](https:\/\/www.atlassian.com\/collections\/strategy)\n- [Service management](https:\/\/www.atlassian.com\/collections\/service)\n- [Software development](https:\/\/www.atlassian.com\/collections\/software)\n\n## By Team\n- [Software](https:\/\/www.atlassian.com\/collections\/software)\n- [Marketing](https:\/\/www.atlassian.com\/teams\/marketing)\n- [IT](https:\/\/www.atlassian.com\/teams\/it)\n- [Product](https:\/\/www.atlassian.com\/software\/jira\/product-discovery%20)\n\n## By Size\n- [Enterprise](https:\/\/www.atlassian.com\/enterprise)\n- [Small Business](https:\/\/www.atlassian.com\/software\/small-business)\n- [Startup](https:\/\/www.atlassian.com\/software\/startups)\n- [Non-profit](https:\/\/www.atlassian.com\/teams\/nonprofits)\n\n## By Industry\n- [Retail](https:\/\/www.atlassian.com\/industries\/retail)\n- [Telecommunications](https:\/\/www.atlassian.com\/industries\/telecom)\n- [Professional Services](https:\/\/www.atlassian.com\/industries\/professional-services)\n- [Government](https:\/\/www.atlassian.com\/government)\n\n[Rovo AI-powered apps – driven by your team's knowledge.](https:\/\/www.atlassian.com\/software\/rovo)\n\nWhy Atlassian\n\n[System of Work NewAtlassian's blueprint for how teams work together](https:\/\/www.atlassian.com\/system-of-work)\n\n[MarketplaceConnect thousands of apps to your Atlassian products](https:\/\/marketplace.atlassian.com\/)\n\n[CustomersCase studies & stories powered by teamwork](https:\/\/www.atlassian.com\/customers)\n\n[FedRAMPCompliant solutions for the public sector](https:\/\/www.atlassian.com\/trust\/compliance\/resources\/fedramp)\n\n[ResilienceEnterprise-grade & highly performant infrastructure](https:\/\/www.atlassian.com\/trust\/resilience)\n\n[PlatformOur deeply integrated, reliable & secure platform](https:\/\/www.atlassian.com\/platform)\n\n[Trust centerEnsure your data's security, compliance & availability](https:\/\/www.atlassian.com\/trust)\n\nResources\n\n[Customer SupportAsk questions, report bugs & give us feedback](https:\/\/support.atlassian.com\/)\n\n[Find PartnersConsulting, training & product customization support](https:\/\/partnerdirectory.atlassian.com\/)\n\n[Atlassian AscendResources and support for your transformation](https:\/\/www.atlassian.com\/migration)\n\n[CommunityLearn, connect and grow with the Atlassian Community](https:\/\/community.atlassian.com\/)\n\nSupport\n\n- [General Inquiries](https:\/\/www.atlassian.com\/company\/contact\/general-inquiries)\n- [Technical Support](https:\/\/support.atlassian.com\/contact\/)\n- [Product Advice](https:\/\/www.atlassian.com\/company\/contact\/product-evaluator-advice)\n- [Pricing and Billing](https:\/\/www.atlassian.com\/company\/contact\/purchasing-licensing)\n- [Partner Support](https:\/\/www.atlassian.com\/partners)\n- [Developer Support](https:\/\/developer.atlassian.com\/)\n- [Enterprise Support](https:\/\/www.atlassian.com\/enterprise\/services)\n- [Purchasing and Licensing](https:\/\/www.atlassian.com\/licensing\/purchase-licensing)\n\nResources\n\n- [Project Management](https:\/\/www.atlassian.com\/project-management)\n- [Project Collaboration](https:\/\/www.atlassian.com\/work-management\/project-collaboration)\n- [Agile](https:\/\/www.atlassian.com\/agile)\n- [Team Playbook](https:\/\/www.atlassian.com\/team-playbook)\n- [Atlassian Learning](https:\/\/community.atlassian.com\/learning)\n- [Product Documentation](https:\/\/confluence.atlassian.com\/display\/ALLDOC\/Atlassian+Documentation)\n- [Get Started](https:\/\/www.atlassian.com\/get-started)\n\nGit topics\n\n- Learn Git\n  \n  - [Git commands](https:\/\/www.atlassian.com\/git\/glossary)\n  - [Learn Git with Bitbucket Cloud](https:\/\/www.atlassian.com\/git\/tutorials\/learn-git-with-bitbucket-cloud)\n  - [Learn about code review in Bitbucket Cloud](https:\/\/www.atlassian.com\/git\/tutorials\/learn-about-code-review-in-bitbucket-cloud)\n  - [Learn Branching with Bitbucket Cloud](https:\/\/www.atlassian.com\/git\/tutorials\/learn-branching-with-bitbucket-cloud)\n  - [Learn Undoing Changes with Bitbucket Cloud](https:\/\/www.atlassian.com\/git\/tutorials\/learn-undoing-changes-with-bitbucket)\n- Beginner\n  \n  - [What is version control](https:\/\/www.atlassian.com\/git\/tutorials\/what-is-version-control)\n  - [Source Code Management](https:\/\/www.atlassian.com\/git\/tutorials\/source-code-management)\n  - [What is Git](https:\/\/www.atlassian.com\/git\/tutorials\/what-is-git)\n  - [Why Git for your organization](https:\/\/www.atlassian.com\/git\/tutorials\/why-git)\n  - [Install Git](https:\/\/www.atlassian.com\/git\/tutorials\/install-git)\n  - [Git SSH](https:\/\/www.atlassian.com\/git\/tutorials\/git-ssh)\n  - [Git archive](https:\/\/www.atlassian.com\/git\/tutorials\/export-git-archive)\n  - [GitOps](https:\/\/www.atlassian.com\/git\/tutorials\/gitops)\n  - [Git cheat sheet](https:\/\/www.atlassian.com\/git\/tutorials\/atlassian-git-cheatsheet)\n- Getting started\n  \n  - Setting up a repository\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/setting-up-a-repository)\n    - [git init](https:\/\/www.atlassian.com\/git\/tutorials\/setting-up-a-repository\/git-init)\n    - [git clone](https:\/\/www.atlassian.com\/git\/tutorials\/setting-up-a-repository\/git-clone)\n    - [git config](https:\/\/www.atlassian.com\/git\/tutorials\/setting-up-a-repository\/git-config)\n    - [git alias](https:\/\/www.atlassian.com\/git\/tutorials\/git-alias)\n  - Saving changes (Git add)\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/saving-changes)\n    - [git commit](https:\/\/www.atlassian.com\/git\/tutorials\/saving-changes\/git-commit)\n    - [git diff](https:\/\/www.atlassian.com\/git\/tutorials\/saving-changes\/git-diff)\n    - [git stash](https:\/\/www.atlassian.com\/git\/tutorials\/saving-changes\/git-stash)\n    - [.gitignore](https:\/\/www.atlassian.com\/git\/tutorials\/saving-changes\/gitignore)\n  - Inspecting a repository\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/inspecting-a-repository)\n    - [git tag](https:\/\/www.atlassian.com\/git\/tutorials\/inspecting-a-repository\/git-tag)\n    - [git blame](https:\/\/www.atlassian.com\/git\/tutorials\/inspecting-a-repository\/git-blame)\n  - Undoing changes\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/undoing-changes)\n    - [git clean](https:\/\/www.atlassian.com\/git\/tutorials\/undoing-changes\/git-clean)\n    - [git revert](https:\/\/www.atlassian.com\/git\/tutorials\/undoing-changes\/git-revert)\n    - [git reset](https:\/\/www.atlassian.com\/git\/tutorials\/undoing-changes\/git-reset)\n    - [git rm](https:\/\/www.atlassian.com\/git\/tutorials\/undoing-changes\/git-rm)\n  - Rewriting history\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/rewriting-history)\n    - [git rebase](https:\/\/www.atlassian.com\/git\/tutorials\/rewriting-history\/git-rebase)\n    - [git reflog](https:\/\/www.atlassian.com\/git\/tutorials\/rewriting-history\/git-reflog)\n- Collaborating workflows\n  \n  - Syncing (git remote)\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/syncing)\n    - [git fetch](https:\/\/www.atlassian.com\/git\/tutorials\/syncing\/git-fetch)\n    - [git push](https:\/\/www.atlassian.com\/git\/tutorials\/syncing\/git-push)\n    - [git pull](https:\/\/www.atlassian.com\/git\/tutorials\/syncing\/git-pull)\n  - [Making a Pull Request](https:\/\/www.atlassian.com\/git\/tutorials\/making-a-pull-request)\n  - Using Branches (Git branch)\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches)\n    - [git checkout](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/git-checkout)\n    - [git merge](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/git-merge)\n    - [Merge conflicts](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/merge-conflicts)\n    - [Merge strategies](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/merge-strategy)\n  - Comparing Workflows\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/comparing-workflows)\n    - [Feature Branch Workflow](https:\/\/www.atlassian.com\/git\/tutorials\/comparing-workflows\/feature-branch-workflow)\n    - [Gitflow Workflow](https:\/\/www.atlassian.com\/git\/tutorials\/comparing-workflows\/gitflow-workflow)\n    - [Forking Workflow](https:\/\/www.atlassian.com\/git\/tutorials\/comparing-workflows\/forking-workflow)\n- Migrating to Git\n  \n  - [SVN to Git - prepping for the migration](https:\/\/www.atlassian.com\/git\/tutorials\/svn-to-git-prepping-your-team-migration)\n  - Migrate to Git from SVN\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/migrating-overview)\n    - [Prepare](https:\/\/www.atlassian.com\/git\/tutorials\/migrating-prepare)\n    - [Convert](https:\/\/www.atlassian.com\/git\/tutorials\/migrating-convert)\n    - [Synchronize](https:\/\/www.atlassian.com\/git\/tutorials\/migrating-synchronize)\n    - [Share](https:\/\/www.atlassian.com\/git\/tutorials\/migrating-share)\n    - [Migrate](https:\/\/www.atlassian.com\/git\/tutorials\/migrating-migrate)\n  - [Perforce to Git - why to make the move](https:\/\/www.atlassian.com\/git\/tutorials\/perforce-git)\n  - [Migrating from Perforce to Git](https:\/\/www.atlassian.com\/git\/tutorials\/perforce-git-migration)\n  - [Working with Git and Perforce: integration workflow](https:\/\/www.atlassian.com\/git\/tutorials\/git-p4)\n  - [How to move a Git repository with history](https:\/\/www.atlassian.com\/git\/tutorials\/git-move-repository)\n- Advanced Tips\n  \n  - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/advanced-overview)\n  - [Merging vs. Rebasing](https:\/\/www.atlassian.com\/git\/tutorials\/merging-vs-rebasing)\n  - [Reset, Checkout, and Revert](https:\/\/www.atlassian.com\/git\/tutorials\/resetting-checking-out-and-reverting)\n  - [Advanced Git log](https:\/\/www.atlassian.com\/git\/tutorials\/git-log)\n  - [Git Hooks](https:\/\/www.atlassian.com\/git\/tutorials\/git-hooks)\n  - [Refs and the Reflog](https:\/\/www.atlassian.com\/git\/tutorials\/refs-and-the-reflog)\n  - [Git submodules](https:\/\/www.atlassian.com\/git\/tutorials\/git-submodule)\n  - [Git subtree](https:\/\/www.atlassian.com\/git\/tutorials\/git-subtree)\n  - [Large repositories in Git](https:\/\/www.atlassian.com\/git\/tutorials\/big-repositories)\n  - [Git LFS](https:\/\/www.atlassian.com\/git\/tutorials\/git-lfs)\n  - [Git gc](https:\/\/www.atlassian.com\/git\/tutorials\/git-gc)\n  - [Git prune](https:\/\/www.atlassian.com\/git\/tutorials\/git-prune)\n  - [Git bash](https:\/\/www.atlassian.com\/git\/tutorials\/git-bash)\n  - [How to store dotfiles](https:\/\/www.atlassian.com\/git\/tutorials\/dotfiles)\n  - [Git cherry pick](https:\/\/www.atlassian.com\/git\/tutorials\/cherry-pick)\n  - [GitK](https:\/\/www.atlassian.com\/git\/tutorials\/gitk)\n  - [Git-show](https:\/\/www.atlassian.com\/git\/tutorials\/git-show)\n- Articles\n  \n  - [Dealing with Maven dependencies when switching to Git](https:\/\/www.atlassian.com\/git\/articles\/maven-dependencies-versions-merging)\n  - [Pull request proficiency: Fetching abilities unlocked\\!](https:\/\/www.atlassian.com\/git\/articles\/pull-request-proficiency-fetching-abilities-unlocked)\n  - [Git and project dependencies](https:\/\/www.atlassian.com\/git\/articles\/git-and-project-dependencies)\n  - [Git or SVN? How Nuance Healthcare Chose a Git Branching Model](https:\/\/www.atlassian.com\/git\/articles\/git-or-svn-git-branching-model)\n  - [Git Forks And Upstreams: How-to and a cool tip](https:\/\/www.atlassian.com\/git\/tutorials\/git-forks-and-upstreams)\n  - [Core concept, workflows and tips](https:\/\/www.atlassian.com\/git\/articles\/core-concept-workflows-and-tips)\n\nGit topics\n\n- Learn Git\n  \n  - [Git commands](https:\/\/www.atlassian.com\/git\/glossary)\n  - [Learn Git with Bitbucket Cloud](https:\/\/www.atlassian.com\/git\/tutorials\/learn-git-with-bitbucket-cloud)\n  - [Learn about code review in Bitbucket Cloud](https:\/\/www.atlassian.com\/git\/tutorials\/learn-about-code-review-in-bitbucket-cloud)\n  - [Learn Branching with Bitbucket Cloud](https:\/\/www.atlassian.com\/git\/tutorials\/learn-branching-with-bitbucket-cloud)\n  - [Learn Undoing Changes with Bitbucket Cloud](https:\/\/www.atlassian.com\/git\/tutorials\/learn-undoing-changes-with-bitbucket)\n- Beginner\n  \n  - [What is version control](https:\/\/www.atlassian.com\/git\/tutorials\/what-is-version-control)\n  - [Source Code Management](https:\/\/www.atlassian.com\/git\/tutorials\/source-code-management)\n  - [What is Git](https:\/\/www.atlassian.com\/git\/tutorials\/what-is-git)\n  - [Why Git for your organization](https:\/\/www.atlassian.com\/git\/tutorials\/why-git)\n  - [Install Git](https:\/\/www.atlassian.com\/git\/tutorials\/install-git)\n  - [Git SSH](https:\/\/www.atlassian.com\/git\/tutorials\/git-ssh)\n  - [Git archive](https:\/\/www.atlassian.com\/git\/tutorials\/export-git-archive)\n  - [GitOps](https:\/\/www.atlassian.com\/git\/tutorials\/gitops)\n  - [Git cheat sheet](https:\/\/www.atlassian.com\/git\/tutorials\/atlassian-git-cheatsheet)\n- Getting started\n  \n  - Setting up a repository\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/setting-up-a-repository)\n    - [git init](https:\/\/www.atlassian.com\/git\/tutorials\/setting-up-a-repository\/git-init)\n    - [git clone](https:\/\/www.atlassian.com\/git\/tutorials\/setting-up-a-repository\/git-clone)\n    - [git config](https:\/\/www.atlassian.com\/git\/tutorials\/setting-up-a-repository\/git-config)\n    - [git alias](https:\/\/www.atlassian.com\/git\/tutorials\/git-alias)\n  - Saving changes (Git add)\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/saving-changes)\n    - [git commit](https:\/\/www.atlassian.com\/git\/tutorials\/saving-changes\/git-commit)\n    - [git diff](https:\/\/www.atlassian.com\/git\/tutorials\/saving-changes\/git-diff)\n    - [git stash](https:\/\/www.atlassian.com\/git\/tutorials\/saving-changes\/git-stash)\n    - [.gitignore](https:\/\/www.atlassian.com\/git\/tutorials\/saving-changes\/gitignore)\n  - Inspecting a repository\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/inspecting-a-repository)\n    - [git tag](https:\/\/www.atlassian.com\/git\/tutorials\/inspecting-a-repository\/git-tag)\n    - [git blame](https:\/\/www.atlassian.com\/git\/tutorials\/inspecting-a-repository\/git-blame)\n  - Undoing changes\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/undoing-changes)\n    - [git clean](https:\/\/www.atlassian.com\/git\/tutorials\/undoing-changes\/git-clean)\n    - [git revert](https:\/\/www.atlassian.com\/git\/tutorials\/undoing-changes\/git-revert)\n    - [git reset](https:\/\/www.atlassian.com\/git\/tutorials\/undoing-changes\/git-reset)\n    - [git rm](https:\/\/www.atlassian.com\/git\/tutorials\/undoing-changes\/git-rm)\n  - Rewriting history\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/rewriting-history)\n    - [git rebase](https:\/\/www.atlassian.com\/git\/tutorials\/rewriting-history\/git-rebase)\n    - [git reflog](https:\/\/www.atlassian.com\/git\/tutorials\/rewriting-history\/git-reflog)\n- Collaborating workflows\n  \n  - Syncing (git remote)\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/syncing)\n    - [git fetch](https:\/\/www.atlassian.com\/git\/tutorials\/syncing\/git-fetch)\n    - [git push](https:\/\/www.atlassian.com\/git\/tutorials\/syncing\/git-push)\n    - [git pull](https:\/\/www.atlassian.com\/git\/tutorials\/syncing\/git-pull)\n  - [Making a Pull Request](https:\/\/www.atlassian.com\/git\/tutorials\/making-a-pull-request)\n  - Using Branches (Git branch)\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches)\n    - [git checkout](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/git-checkout)\n    - [git merge](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/git-merge)\n    - [Merge conflicts](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/merge-conflicts)\n    - [Merge strategies](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/merge-strategy)\n  - Comparing Workflows\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/comparing-workflows)\n    - [Feature Branch Workflow](https:\/\/www.atlassian.com\/git\/tutorials\/comparing-workflows\/feature-branch-workflow)\n    - [Gitflow Workflow](https:\/\/www.atlassian.com\/git\/tutorials\/comparing-workflows\/gitflow-workflow)\n    - [Forking Workflow](https:\/\/www.atlassian.com\/git\/tutorials\/comparing-workflows\/forking-workflow)\n- Migrating to Git\n  \n  - [SVN to Git - prepping for the migration](https:\/\/www.atlassian.com\/git\/tutorials\/svn-to-git-prepping-your-team-migration)\n  - Migrate to Git from SVN\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/migrating-overview)\n    - [Prepare](https:\/\/www.atlassian.com\/git\/tutorials\/migrating-prepare)\n    - [Convert](https:\/\/www.atlassian.com\/git\/tutorials\/migrating-convert)\n    - [Synchronize](https:\/\/www.atlassian.com\/git\/tutorials\/migrating-synchronize)\n    - [Share](https:\/\/www.atlassian.com\/git\/tutorials\/migrating-share)\n    - [Migrate](https:\/\/www.atlassian.com\/git\/tutorials\/migrating-migrate)\n  - [Perforce to Git - why to make the move](https:\/\/www.atlassian.com\/git\/tutorials\/perforce-git)\n  - [Migrating from Perforce to Git](https:\/\/www.atlassian.com\/git\/tutorials\/perforce-git-migration)\n  - [Working with Git and Perforce: integration workflow](https:\/\/www.atlassian.com\/git\/tutorials\/git-p4)\n  - [How to move a Git repository with history](https:\/\/www.atlassian.com\/git\/tutorials\/git-move-repository)\n- Advanced Tips\n  \n  - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/advanced-overview)\n  - [Merging vs. Rebasing](https:\/\/www.atlassian.com\/git\/tutorials\/merging-vs-rebasing)\n  - [Reset, Checkout, and Revert](https:\/\/www.atlassian.com\/git\/tutorials\/resetting-checking-out-and-reverting)\n  - [Advanced Git log](https:\/\/www.atlassian.com\/git\/tutorials\/git-log)\n  - [Git Hooks](https:\/\/www.atlassian.com\/git\/tutorials\/git-hooks)\n  - [Refs and the Reflog](https:\/\/www.atlassian.com\/git\/tutorials\/refs-and-the-reflog)\n  - [Git submodules](https:\/\/www.atlassian.com\/git\/tutorials\/git-submodule)\n  - [Git subtree](https:\/\/www.atlassian.com\/git\/tutorials\/git-subtree)\n  - [Large repositories in Git](https:\/\/www.atlassian.com\/git\/tutorials\/big-repositories)\n  - [Git LFS](https:\/\/www.atlassian.com\/git\/tutorials\/git-lfs)\n  - [Git gc](https:\/\/www.atlassian.com\/git\/tutorials\/git-gc)\n  - [Git prune](https:\/\/www.atlassian.com\/git\/tutorials\/git-prune)\n  - [Git bash](https:\/\/www.atlassian.com\/git\/tutorials\/git-bash)\n  - [How to store dotfiles](https:\/\/www.atlassian.com\/git\/tutorials\/dotfiles)\n  - [Git cherry pick](https:\/\/www.atlassian.com\/git\/tutorials\/cherry-pick)\n  - [GitK](https:\/\/www.atlassian.com\/git\/tutorials\/gitk)\n  - [Git-show](https:\/\/www.atlassian.com\/git\/tutorials\/git-show)\n- Articles\n  \n  - [Dealing with Maven dependencies when switching to Git](https:\/\/www.atlassian.com\/git\/articles\/maven-dependencies-versions-merging)\n  - [Pull request proficiency: Fetching abilities unlocked\\!](https:\/\/www.atlassian.com\/git\/articles\/pull-request-proficiency-fetching-abilities-unlocked)\n  - [Git and project dependencies](https:\/\/www.atlassian.com\/git\/articles\/git-and-project-dependencies)\n  - [Git or SVN? How Nuance Healthcare Chose a Git Branching Model](https:\/\/www.atlassian.com\/git\/articles\/git-or-svn-git-branching-model)\n  - [Git Forks And Upstreams: How-to and a cool tip](https:\/\/www.atlassian.com\/git\/tutorials\/git-forks-and-upstreams)\n  - [Core concept, workflows and tips](https:\/\/www.atlassian.com\/git\/articles\/core-concept-workflows-and-tips)\n\nGit topics\n\n- Learn Git\n  \n  - [Git commands](https:\/\/www.atlassian.com\/git\/glossary)\n  - [Learn Git with Bitbucket Cloud](https:\/\/www.atlassian.com\/git\/tutorials\/learn-git-with-bitbucket-cloud)\n  - [Learn about code review in Bitbucket Cloud](https:\/\/www.atlassian.com\/git\/tutorials\/learn-about-code-review-in-bitbucket-cloud)\n  - [Learn Branching with Bitbucket Cloud](https:\/\/www.atlassian.com\/git\/tutorials\/learn-branching-with-bitbucket-cloud)\n  - [Learn Undoing Changes with Bitbucket Cloud](https:\/\/www.atlassian.com\/git\/tutorials\/learn-undoing-changes-with-bitbucket)\n- Beginner\n  \n  - [What is version control](https:\/\/www.atlassian.com\/git\/tutorials\/what-is-version-control)\n  - [Source Code Management](https:\/\/www.atlassian.com\/git\/tutorials\/source-code-management)\n  - [What is Git](https:\/\/www.atlassian.com\/git\/tutorials\/what-is-git)\n  - [Why Git for your organization](https:\/\/www.atlassian.com\/git\/tutorials\/why-git)\n  - [Install Git](https:\/\/www.atlassian.com\/git\/tutorials\/install-git)\n  - [Git SSH](https:\/\/www.atlassian.com\/git\/tutorials\/git-ssh)\n  - [Git archive](https:\/\/www.atlassian.com\/git\/tutorials\/export-git-archive)\n  - [GitOps](https:\/\/www.atlassian.com\/git\/tutorials\/gitops)\n  - [Git cheat sheet](https:\/\/www.atlassian.com\/git\/tutorials\/atlassian-git-cheatsheet)\n- Getting started\n  \n  - Setting up a repository\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/setting-up-a-repository)\n    - [git init](https:\/\/www.atlassian.com\/git\/tutorials\/setting-up-a-repository\/git-init)\n    - [git clone](https:\/\/www.atlassian.com\/git\/tutorials\/setting-up-a-repository\/git-clone)\n    - [git config](https:\/\/www.atlassian.com\/git\/tutorials\/setting-up-a-repository\/git-config)\n    - [git alias](https:\/\/www.atlassian.com\/git\/tutorials\/git-alias)\n  - Saving changes (Git add)\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/saving-changes)\n    - [git commit](https:\/\/www.atlassian.com\/git\/tutorials\/saving-changes\/git-commit)\n    - [git diff](https:\/\/www.atlassian.com\/git\/tutorials\/saving-changes\/git-diff)\n    - [git stash](https:\/\/www.atlassian.com\/git\/tutorials\/saving-changes\/git-stash)\n    - [.gitignore](https:\/\/www.atlassian.com\/git\/tutorials\/saving-changes\/gitignore)\n  - Inspecting a repository\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/inspecting-a-repository)\n    - [git tag](https:\/\/www.atlassian.com\/git\/tutorials\/inspecting-a-repository\/git-tag)\n    - [git blame](https:\/\/www.atlassian.com\/git\/tutorials\/inspecting-a-repository\/git-blame)\n  - Undoing changes\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/undoing-changes)\n    - [git clean](https:\/\/www.atlassian.com\/git\/tutorials\/undoing-changes\/git-clean)\n    - [git revert](https:\/\/www.atlassian.com\/git\/tutorials\/undoing-changes\/git-revert)\n    - [git reset](https:\/\/www.atlassian.com\/git\/tutorials\/undoing-changes\/git-reset)\n    - [git rm](https:\/\/www.atlassian.com\/git\/tutorials\/undoing-changes\/git-rm)\n  - Rewriting history\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/rewriting-history)\n    - [git rebase](https:\/\/www.atlassian.com\/git\/tutorials\/rewriting-history\/git-rebase)\n    - [git reflog](https:\/\/www.atlassian.com\/git\/tutorials\/rewriting-history\/git-reflog)\n- Collaborating workflows\n  \n  - Syncing (git remote)\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/syncing)\n    - [git fetch](https:\/\/www.atlassian.com\/git\/tutorials\/syncing\/git-fetch)\n    - [git push](https:\/\/www.atlassian.com\/git\/tutorials\/syncing\/git-push)\n    - [git pull](https:\/\/www.atlassian.com\/git\/tutorials\/syncing\/git-pull)\n  - [Making a Pull Request](https:\/\/www.atlassian.com\/git\/tutorials\/making-a-pull-request)\n  - Using Branches (Git branch)\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches)\n    - [git checkout](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/git-checkout)\n    - [git merge](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/git-merge)\n    - [Merge conflicts](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/merge-conflicts)\n    - [Merge strategies](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/merge-strategy)\n  - Comparing Workflows\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/comparing-workflows)\n    - [Feature Branch Workflow](https:\/\/www.atlassian.com\/git\/tutorials\/comparing-workflows\/feature-branch-workflow)\n    - [Gitflow Workflow](https:\/\/www.atlassian.com\/git\/tutorials\/comparing-workflows\/gitflow-workflow)\n    - [Forking Workflow](https:\/\/www.atlassian.com\/git\/tutorials\/comparing-workflows\/forking-workflow)\n- Migrating to Git\n  \n  - [SVN to Git - prepping for the migration](https:\/\/www.atlassian.com\/git\/tutorials\/svn-to-git-prepping-your-team-migration)\n  - Migrate to Git from SVN\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/migrating-overview)\n    - [Prepare](https:\/\/www.atlassian.com\/git\/tutorials\/migrating-prepare)\n    - [Convert](https:\/\/www.atlassian.com\/git\/tutorials\/migrating-convert)\n    - [Synchronize](https:\/\/www.atlassian.com\/git\/tutorials\/migrating-synchronize)\n    - [Share](https:\/\/www.atlassian.com\/git\/tutorials\/migrating-share)\n    - [Migrate](https:\/\/www.atlassian.com\/git\/tutorials\/migrating-migrate)\n  - [Perforce to Git - why to make the move](https:\/\/www.atlassian.com\/git\/tutorials\/perforce-git)\n  - [Migrating from Perforce to Git](https:\/\/www.atlassian.com\/git\/tutorials\/perforce-git-migration)\n  - [Working with Git and Perforce: integration workflow](https:\/\/www.atlassian.com\/git\/tutorials\/git-p4)\n  - [How to move a Git repository with history](https:\/\/www.atlassian.com\/git\/tutorials\/git-move-repository)\n- Advanced Tips\n  \n  - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/advanced-overview)\n  - [Merging vs. Rebasing](https:\/\/www.atlassian.com\/git\/tutorials\/merging-vs-rebasing)\n  - [Reset, Checkout, and Revert](https:\/\/www.atlassian.com\/git\/tutorials\/resetting-checking-out-and-reverting)\n  - [Advanced Git log](https:\/\/www.atlassian.com\/git\/tutorials\/git-log)\n  - [Git Hooks](https:\/\/www.atlassian.com\/git\/tutorials\/git-hooks)\n  - [Refs and the Reflog](https:\/\/www.atlassian.com\/git\/tutorials\/refs-and-the-reflog)\n  - [Git submodules](https:\/\/www.atlassian.com\/git\/tutorials\/git-submodule)\n  - [Git subtree](https:\/\/www.atlassian.com\/git\/tutorials\/git-subtree)\n  - [Large repositories in Git](https:\/\/www.atlassian.com\/git\/tutorials\/big-repositories)\n  - [Git LFS](https:\/\/www.atlassian.com\/git\/tutorials\/git-lfs)\n  - [Git gc](https:\/\/www.atlassian.com\/git\/tutorials\/git-gc)\n  - [Git prune](https:\/\/www.atlassian.com\/git\/tutorials\/git-prune)\n  - [Git bash](https:\/\/www.atlassian.com\/git\/tutorials\/git-bash)\n  - [How to store dotfiles](https:\/\/www.atlassian.com\/git\/tutorials\/dotfiles)\n  - [Git cherry pick](https:\/\/www.atlassian.com\/git\/tutorials\/cherry-pick)\n  - [GitK](https:\/\/www.atlassian.com\/git\/tutorials\/gitk)\n  - [Git-show](https:\/\/www.atlassian.com\/git\/tutorials\/git-show)\n- Articles\n  \n  - [Dealing with Maven dependencies when switching to Git](https:\/\/www.atlassian.com\/git\/articles\/maven-dependencies-versions-merging)\n  - [Pull request proficiency: Fetching abilities unlocked\\!](https:\/\/www.atlassian.com\/git\/articles\/pull-request-proficiency-fetching-abilities-unlocked)\n  - [Git and project dependencies](https:\/\/www.atlassian.com\/git\/articles\/git-and-project-dependencies)\n  - [Git or SVN? How Nuance Healthcare Chose a Git Branching Model](https:\/\/www.atlassian.com\/git\/articles\/git-or-svn-git-branching-model)\n  - [Git Forks And Upstreams: How-to and a cool tip](https:\/\/www.atlassian.com\/git\/tutorials\/git-forks-and-upstreams)\n  - [Core concept, workflows and tips](https:\/\/www.atlassian.com\/git\/articles\/core-concept-workflows-and-tips)\n\nGit topics\n\n- Learn Git\n  \n  - [Git commands](https:\/\/www.atlassian.com\/git\/glossary)\n  - [Learn Git with Bitbucket Cloud](https:\/\/www.atlassian.com\/git\/tutorials\/learn-git-with-bitbucket-cloud)\n  - [Learn about code review in Bitbucket Cloud](https:\/\/www.atlassian.com\/git\/tutorials\/learn-about-code-review-in-bitbucket-cloud)\n  - [Learn Branching with Bitbucket Cloud](https:\/\/www.atlassian.com\/git\/tutorials\/learn-branching-with-bitbucket-cloud)\n  - [Learn Undoing Changes with Bitbucket Cloud](https:\/\/www.atlassian.com\/git\/tutorials\/learn-undoing-changes-with-bitbucket)\n- Beginner\n  \n  - [What is version control](https:\/\/www.atlassian.com\/git\/tutorials\/what-is-version-control)\n  - [Source Code Management](https:\/\/www.atlassian.com\/git\/tutorials\/source-code-management)\n  - [What is Git](https:\/\/www.atlassian.com\/git\/tutorials\/what-is-git)\n  - [Why Git for your organization](https:\/\/www.atlassian.com\/git\/tutorials\/why-git)\n  - [Install Git](https:\/\/www.atlassian.com\/git\/tutorials\/install-git)\n  - [Git SSH](https:\/\/www.atlassian.com\/git\/tutorials\/git-ssh)\n  - [Git archive](https:\/\/www.atlassian.com\/git\/tutorials\/export-git-archive)\n  - [GitOps](https:\/\/www.atlassian.com\/git\/tutorials\/gitops)\n  - [Git cheat sheet](https:\/\/www.atlassian.com\/git\/tutorials\/atlassian-git-cheatsheet)\n- Getting started\n  \n  - Setting up a repository\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/setting-up-a-repository)\n    - [git init](https:\/\/www.atlassian.com\/git\/tutorials\/setting-up-a-repository\/git-init)\n    - [git clone](https:\/\/www.atlassian.com\/git\/tutorials\/setting-up-a-repository\/git-clone)\n    - [git config](https:\/\/www.atlassian.com\/git\/tutorials\/setting-up-a-repository\/git-config)\n    - [git alias](https:\/\/www.atlassian.com\/git\/tutorials\/git-alias)\n  - Saving changes (Git add)\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/saving-changes)\n    - [git commit](https:\/\/www.atlassian.com\/git\/tutorials\/saving-changes\/git-commit)\n    - [git diff](https:\/\/www.atlassian.com\/git\/tutorials\/saving-changes\/git-diff)\n    - [git stash](https:\/\/www.atlassian.com\/git\/tutorials\/saving-changes\/git-stash)\n    - [.gitignore](https:\/\/www.atlassian.com\/git\/tutorials\/saving-changes\/gitignore)\n  - Inspecting a repository\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/inspecting-a-repository)\n    - [git tag](https:\/\/www.atlassian.com\/git\/tutorials\/inspecting-a-repository\/git-tag)\n    - [git blame](https:\/\/www.atlassian.com\/git\/tutorials\/inspecting-a-repository\/git-blame)\n  - Undoing changes\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/undoing-changes)\n    - [git clean](https:\/\/www.atlassian.com\/git\/tutorials\/undoing-changes\/git-clean)\n    - [git revert](https:\/\/www.atlassian.com\/git\/tutorials\/undoing-changes\/git-revert)\n    - [git reset](https:\/\/www.atlassian.com\/git\/tutorials\/undoing-changes\/git-reset)\n    - [git rm](https:\/\/www.atlassian.com\/git\/tutorials\/undoing-changes\/git-rm)\n  - Rewriting history\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/rewriting-history)\n    - [git rebase](https:\/\/www.atlassian.com\/git\/tutorials\/rewriting-history\/git-rebase)\n    - [git reflog](https:\/\/www.atlassian.com\/git\/tutorials\/rewriting-history\/git-reflog)\n- Collaborating workflows\n  \n  - Syncing (git remote)\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/syncing)\n    - [git fetch](https:\/\/www.atlassian.com\/git\/tutorials\/syncing\/git-fetch)\n    - [git push](https:\/\/www.atlassian.com\/git\/tutorials\/syncing\/git-push)\n    - [git pull](https:\/\/www.atlassian.com\/git\/tutorials\/syncing\/git-pull)\n  - [Making a Pull Request](https:\/\/www.atlassian.com\/git\/tutorials\/making-a-pull-request)\n  - Using Branches (Git branch)\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches)\n    - [git checkout](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/git-checkout)\n    - [git merge](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/git-merge)\n    - [Merge conflicts](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/merge-conflicts)\n    - [Merge strategies](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/merge-strategy)\n  - Comparing Workflows\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/comparing-workflows)\n    - [Feature Branch Workflow](https:\/\/www.atlassian.com\/git\/tutorials\/comparing-workflows\/feature-branch-workflow)\n    - [Gitflow Workflow](https:\/\/www.atlassian.com\/git\/tutorials\/comparing-workflows\/gitflow-workflow)\n    - [Forking Workflow](https:\/\/www.atlassian.com\/git\/tutorials\/comparing-workflows\/forking-workflow)\n- Migrating to Git\n  \n  - [SVN to Git - prepping for the migration](https:\/\/www.atlassian.com\/git\/tutorials\/svn-to-git-prepping-your-team-migration)\n  - Migrate to Git from SVN\n    \n    - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/migrating-overview)\n    - [Prepare](https:\/\/www.atlassian.com\/git\/tutorials\/migrating-prepare)\n    - [Convert](https:\/\/www.atlassian.com\/git\/tutorials\/migrating-convert)\n    - [Synchronize](https:\/\/www.atlassian.com\/git\/tutorials\/migrating-synchronize)\n    - [Share](https:\/\/www.atlassian.com\/git\/tutorials\/migrating-share)\n    - [Migrate](https:\/\/www.atlassian.com\/git\/tutorials\/migrating-migrate)\n  - [Perforce to Git - why to make the move](https:\/\/www.atlassian.com\/git\/tutorials\/perforce-git)\n  - [Migrating from Perforce to Git](https:\/\/www.atlassian.com\/git\/tutorials\/perforce-git-migration)\n  - [Working with Git and Perforce: integration workflow](https:\/\/www.atlassian.com\/git\/tutorials\/git-p4)\n  - [How to move a Git repository with history](https:\/\/www.atlassian.com\/git\/tutorials\/git-move-repository)\n- Advanced Tips\n  \n  - [Overview](https:\/\/www.atlassian.com\/git\/tutorials\/advanced-overview)\n  - [Merging vs. Rebasing](https:\/\/www.atlassian.com\/git\/tutorials\/merging-vs-rebasing)\n  - [Reset, Checkout, and Revert](https:\/\/www.atlassian.com\/git\/tutorials\/resetting-checking-out-and-reverting)\n  - [Advanced Git log](https:\/\/www.atlassian.com\/git\/tutorials\/git-log)\n  - [Git Hooks](https:\/\/www.atlassian.com\/git\/tutorials\/git-hooks)\n  - [Refs and the Reflog](https:\/\/www.atlassian.com\/git\/tutorials\/refs-and-the-reflog)\n  - [Git submodules](https:\/\/www.atlassian.com\/git\/tutorials\/git-submodule)\n  - [Git subtree](https:\/\/www.atlassian.com\/git\/tutorials\/git-subtree)\n  - [Large repositories in Git](https:\/\/www.atlassian.com\/git\/tutorials\/big-repositories)\n  - [Git LFS](https:\/\/www.atlassian.com\/git\/tutorials\/git-lfs)\n  - [Git gc](https:\/\/www.atlassian.com\/git\/tutorials\/git-gc)\n  - [Git prune](https:\/\/www.atlassian.com\/git\/tutorials\/git-prune)\n  - [Git bash](https:\/\/www.atlassian.com\/git\/tutorials\/git-bash)\n  - [How to store dotfiles](https:\/\/www.atlassian.com\/git\/tutorials\/dotfiles)\n  - [Git cherry pick](https:\/\/www.atlassian.com\/git\/tutorials\/cherry-pick)\n  - [GitK](https:\/\/www.atlassian.com\/git\/tutorials\/gitk)\n  - [Git-show](https:\/\/www.atlassian.com\/git\/tutorials\/git-show)\n- Articles\n  \n  - [Dealing with Maven dependencies when switching to Git](https:\/\/www.atlassian.com\/git\/articles\/maven-dependencies-versions-merging)\n  - [Pull request proficiency: Fetching abilities unlocked\\!](https:\/\/www.atlassian.com\/git\/articles\/pull-request-proficiency-fetching-abilities-unlocked)\n  - [Git and project dependencies](https:\/\/www.atlassian.com\/git\/articles\/git-and-project-dependencies)\n  - [Git or SVN? How Nuance Healthcare Chose a Git Branching Model](https:\/\/www.atlassian.com\/git\/articles\/git-or-svn-git-branching-model)\n  - [Git Forks And Upstreams: How-to and a cool tip](https:\/\/www.atlassian.com\/git\/tutorials\/git-forks-and-upstreams)\n  - [Core concept, workflows and tips](https:\/\/www.atlassian.com\/git\/articles\/core-concept-workflows-and-tips)\n\n# Git checkout\nThis page is an examination of the `git checkout` command. It will cover usage examples and edge cases. In Git terms, a \"checkout\" is the act of switching between different versions of a target entity. The `git checkout` command operates upon three distinct entities: files, commits, and branches. In addition to the definition of \"checkout\" the phrase \"checking out\" is commonly used to imply the act of executing the `git checkout` command. In the [Undoing Changes](https:\/\/www.atlassian.com\/git\/tutorials\/undoing-changes) topic, we saw how `git checkout` can be used to view old commits. The focus for the majority of this document will be checkout operations on branches.\n\nChecking out branches is similar to checking out old commits and files in that the working directory is updated to match the selected branch\/revision; however, new changes are saved in the project history—that is, it’s not a read-only operation.\n\n## Checking out branches\nThe `git checkout` command lets you navigate between the branches created by `git branch`. Checking out a branch updates the files in the working directory to match the version stored in that branch, and it tells Git to record all new commits on that branch. Think of it as a way to select which line of development you’re working on.\n\nHaving a dedicated branch for each new feature is a dramatic shift from a traditional SVN workflow. It makes it ridiculously easy to try new experiments without the fear of destroying existing functionality, and it makes it possible to work on many unrelated features at the same time. In addition, branches also facilitate several collaborative workflows.\n\nThe `git checkout` command may occasionally be confused with `git clone`. The difference between the two commands is that clone works to fetch code from a remote repository, alternatively checkout works to switch between versions of code already on the local system.\n\n## Usage: Existing branches\nAssuming the repo you're working in contains pre-existing branches, you can switch between these branches using `git checkout`. To find out what branches are available and what the current branch name is, execute `git branch`.\n```\n1$＞ git branch \n2main \n3another_branch \n4feature_inprogress_branch \n5$＞ git checkout feature_inprogress_branch\n```\nThe above example demonstrates how to view a list of available branches by executing the `git branch` command, and switch to a specified branch, in this case, the `feature_inprogress_branch`.\n\n## New branches\n`Git checkout` works hand-in-hand with [git branch](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches). The `git branch` command can be used to create a new branch. When you want to start a new feature, you create a new branch off `main` using `git branch new_branch`. Once created you can then use `git checkout new_branch` to switch to that branch. Additionally, The `git checkout` command accepts a `-b` argument that acts as a convenience method which will create the new branch and immediately switch to it. You can work on multiple features in a single repository by switching between them with `git checkout`.\n```\n1git checkout -b ＜new-branch＞\n```\nThe above example simultaneously creates and checks out `＜new-branch＞`. The `-b` option is a convenience flag that tells Git to run `git branch <new-branch>` before running `git checkout ＜new-branch＞`.\n```\n1git checkout -b ＜new-branch＞ ＜existing-branch＞\n```\nBy default `git checkout -b` will base the `new-branch` off the current `HEAD`. An optional additional branch parameter can be passed to `git checkout`. In the above example, `＜existing-branch＞` is passed which then bases `new-branch` off of `existing-branch` instead of the current `HEAD`.\n\n## Switching branches\nSwitching branches is a straightforward operation. Executing the following will point `HEAD` to the tip of `＜branchname＞.`\n```\n1git checkout ＜branchname＞\n```\nGit tracks a history of checkout operations in the reflog. You can execute `git reflog` to view the history.\n\n## Git checkout a remote branch\nWhen collaborating with a team it is common to utilize remote repositories. These repositories may be hosted and shared or they may be another colleague's local copy. Each remote repository will contain its own set of branches. In order to checkout a remote branch you have to first fetch the contents of the branch.\n```\n1git fetch --all\n```\nIn modern versions of Git, you can then checkout the remote branch like a local branch.\n```\n1git checkout ＜remotebranch＞\n```\nOlder versions of Git require the creation of a new branch based on the `remote`.\n```\n1git checkout -b ＜remotebranch＞ origin\/＜remotebranch＞\n```\nAdditionally you can checkout a new local branch and reset it to the remote branches last commit.\n```\n1git checkout -b ＜branchname＞\n2git reset --hard origin\/＜branchname＞\n```\n## Detached HEADS\nNow that we’ve seen the three main uses of `git checkout` on branches, it's important to discuss the `“detached HEAD”` state. Remember that the `HEAD` is Git’s way of referring to the current snapshot. Internally, the `git checkout` command simply updates the `HEAD` to point to either the specified branch or commit. When it points to a branch, Git doesn't complain, but when you check out a commit, it switches into a `“detached HEAD”` state.\n\nThis is a warning telling you that everything you’re doing is “detached” from the rest of your project’s development. If you were to start developing a feature while in a detached `HEAD` state, there would be no branch allowing you to get back to it. When you inevitably check out another branch (e.g., to merge your feature in), there would be no way to reference your feature:\n\n![Attached head vs detached head](https:\/\/dam-cdn.atl.orangelogic.com\/AssetLink\/b01na740f1la476ut2ss5x8pqx7ohq8f.svg)\n\nThe point is, your development should always take place on a branch—never on a detached `HEAD`. This makes sure you always have a reference to your new commits. However, if you’re just looking at an old commit, it doesn’t really matter if you’re in a detached `HEAD` state or not.\n\n## Summary\nThis page focused on usage of the `git checkout` command when changing branches. In summation, `git checkout`, when used on branches, alters the target of the `HEAD` ref. It can be used to create branches, switch branches, and checkout remote branches. The `git checkout` command is an essential tool for standard Git operation. It is a counterpart to [git merge](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/git-merge). The `git checkout` and `git merge` commands are critical tools to enabling [git workflows](https:\/\/www.atlassian.com\/git\/tutorials\/comparing-workflows).\n\n## Recommended for you\n### Bitbucket blog\n[Learn more](https:\/\/www.atlassian.com\/blog\/bitbucket)\n\n### DevOps learning path\n[Learn more](https:\/\/university.atlassian.com\/student\/activity\/2483065-hello-and-welcome)\n\n### Learn more about Git\nFind more Git guides and resources in this hub.\n\n[Read more](https:\/\/www.atlassian.com\/git)\n\n- [Company](https:\/\/www.atlassian.com\/company)\n- [Careers](https:\/\/www.atlassian.com\/company\/careers)\n- [Events](https:\/\/www.atlassian.com\/company\/events)\n- [Blogs](https:\/\/www.atlassian.com\/blog)\n- [Investor Relations](https:\/\/investors.atlassian.com\/)\n- [Atlassian Foundation](https:\/\/www.atlassianfoundation.org\/)\n- [Press kit](https:\/\/www.atlassian.com\/company\/news\/press-kit)\n- [Contact us](https:\/\/www.atlassian.com\/company\/contact)\n\n## Products\n- [Rovo](https:\/\/www.atlassian.com\/rovo)\n- [Jira](https:\/\/www.atlassian.com\/software\/jira)\n- [Jira Align](https:\/\/www.atlassian.com\/software\/jira\/align)\n- [Jira Service Management](https:\/\/www.atlassian.com\/software\/jira\/service-management)\n- [Confluence](https:\/\/www.atlassian.com\/software\/confluence)\n- [Loom](https:\/\/www.atlassian.com\/software\/loom)\n- [Trello](https:\/\/trello.com\/home)\n- [Bitbucket](https:\/\/www.atlassian.com\/software\/bitbucket)\n- [See all products](https:\/\/www.atlassian.com\/software)\n\n## Resources\n- [Technical support](https:\/\/support.atlassian.com\/)\n- [Purchasing & licensing](https:\/\/www.atlassian.com\/licensing\/purchase-licensing)\n- [Atlassian Community](https:\/\/community.atlassian.com\/)\n- [Knowledge base](https:\/\/confluence.atlassian.com\/kb)\n- [Marketplace](https:\/\/marketplace.atlassian.com\/)\n- [My account](https:\/\/my.atlassian.com\/products\/index)\n- [Create support ticket](https:\/\/support.atlassian.com\/contact\/)\n\n## Learn\n- [Partners](https:\/\/www.atlassian.com\/partners)\n- [Training & certification](https:\/\/www.atlassian.com\/university)\n- [Documentation](https:\/\/confluence.atlassian.com\/display\/ALLDOC\/Atlassian+Documentation)\n- [Developer resources](https:\/\/www.atlassian.com\/developers)\n- [Enterprise services](https:\/\/www.atlassian.com\/enterprise\/services)\n- [See all resources](https:\/\/www.atlassian.com\/resources)\n\nCopyright © 2026 Atlassian\n\n- [Privacy policy](https:\/\/www.atlassian.com\/legal\/privacy-policy)\n- [Notice at Collection](https:\/\/www.atlassian.com\/legal\/privacy-policy#additional-disclosures-for-ca-residents)\n- [Terms](https:\/\/www.atlassian.com\/legal\/cloud-terms-of-service)\n- [Impressum](https:\/\/www.atlassian.com\/legal\/impressum)\n\nLanguage selector\n\nEnglish\n\n▾","attrs_readable_markdown":"This page is an examination of the `git checkout` command. It will cover usage examples and edge cases. In Git terms, a \"checkout\" is the act of switching between different versions of a target entity. The `git checkout` command operates upon three distinct entities: files, commits, and branches. In addition to the definition of \"checkout\" the phrase \"checking out\" is commonly used to imply the act of executing the `git checkout` command. In the [Undoing Changes](https:\/\/www.atlassian.com\/git\/tutorials\/undoing-changes) topic, we saw how `git checkout` can be used to view old commits. The focus for the majority of this document will be checkout operations on branches.\n\nChecking out branches is similar to checking out old commits and files in that the working directory is updated to match the selected branch\/revision; however, new changes are saved in the project history—that is, it’s not a read-only operation.\n\nChecking out branches\n\nThe `git checkout` command lets you navigate between the branches created by `git branch`. Checking out a branch updates the files in the working directory to match the version stored in that branch, and it tells Git to record all new commits on that branch. Think of it as a way to select which line of development you’re working on.\n\nHaving a dedicated branch for each new feature is a dramatic shift from a traditional SVN workflow. It makes it ridiculously easy to try new experiments without the fear of destroying existing functionality, and it makes it possible to work on many unrelated features at the same time. In addition, branches also facilitate several collaborative workflows.\n\nThe `git checkout` command may occasionally be confused with `git clone`. The difference between the two commands is that clone works to fetch code from a remote repository, alternatively checkout works to switch between versions of code already on the local system.\n\nUsage: Existing branches\n\nAssuming the repo you're working in contains pre-existing branches, you can switch between these branches using `git checkout`. To find out what branches are available and what the current branch name is, execute `git branch`.\n```\n$＞ git branch \nmain \nanother_branch \nfeature_inprogress_branch \n$＞ git checkout feature_inprogress_branch\n```\nThe above example demonstrates how to view a list of available branches by executing the `git branch` command, and switch to a specified branch, in this case, the `feature_inprogress_branch`.\n\nNew branches\n\n`Git checkout` works hand-in-hand with [git branch](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches). The `git branch` command can be used to create a new branch. When you want to start a new feature, you create a new branch off `main` using `git branch new_branch`. Once created you can then use `git checkout new_branch` to switch to that branch. Additionally, The `git checkout` command accepts a `-b` argument that acts as a convenience method which will create the new branch and immediately switch to it. You can work on multiple features in a single repository by switching between them with `git checkout`.\n```\ngit checkout -b ＜new-branch＞\n```\nThe above example simultaneously creates and checks out `＜new-branch＞`. The `-b` option is a convenience flag that tells Git to run `git branch <new-branch>` before running `git checkout ＜new-branch＞`.\n```\ngit checkout -b ＜new-branch＞ ＜existing-branch＞\n```\nBy default `git checkout -b` will base the `new-branch` off the current `HEAD`. An optional additional branch parameter can be passed to `git checkout`. In the above example, `＜existing-branch＞` is passed which then bases `new-branch` off of `existing-branch` instead of the current `HEAD`.\n\nSwitching branches\n\nSwitching branches is a straightforward operation. Executing the following will point `HEAD` to the tip of `＜branchname＞.`\n```\ngit checkout ＜branchname＞\n```\nGit tracks a history of checkout operations in the reflog. You can execute `git reflog` to view the history.\n\nGit checkout a remote branch\n\nWhen collaborating with a team it is common to utilize remote repositories. These repositories may be hosted and shared or they may be another colleague's local copy. Each remote repository will contain its own set of branches. In order to checkout a remote branch you have to first fetch the contents of the branch.\n```\ngit fetch --all\n```\nIn modern versions of Git, you can then checkout the remote branch like a local branch.\n```\ngit checkout ＜remotebranch＞\n```\nOlder versions of Git require the creation of a new branch based on the `remote`.\n```\ngit checkout -b ＜remotebranch＞ origin\/＜remotebranch＞\n```\nAdditionally you can checkout a new local branch and reset it to the remote branches last commit.\n```\ngit checkout -b ＜branchname＞\ngit reset --hard origin\/＜branchname＞\n```\nDetached HEADS\n\nNow that we’ve seen the three main uses of `git checkout` on branches, it's important to discuss the `“detached HEAD”` state. Remember that the `HEAD` is Git’s way of referring to the current snapshot. Internally, the `git checkout` command simply updates the `HEAD` to point to either the specified branch or commit. When it points to a branch, Git doesn't complain, but when you check out a commit, it switches into a `“detached HEAD”` state.\n\nThis is a warning telling you that everything you’re doing is “detached” from the rest of your project’s development. If you were to start developing a feature while in a detached `HEAD` state, there would be no branch allowing you to get back to it. When you inevitably check out another branch (e.g., to merge your feature in), there would be no way to reference your feature:\n\n![Attached head vs detached head](https:\/\/dam-cdn.atl.orangelogic.com\/AssetLink\/b01na740f1la476ut2ss5x8pqx7ohq8f.svg)\n\nThe point is, your development should always take place on a branch—never on a detached `HEAD`. This makes sure you always have a reference to your new commits. However, if you’re just looking at an old commit, it doesn’t really matter if you’re in a detached `HEAD` state or not.\n\nSummary\n\nThis page focused on usage of the `git checkout` command when changing branches. In summation, `git checkout`, when used on branches, alters the target of the `HEAD` ref. It can be used to create branches, switch branches, and checkout remote branches. The `git checkout` command is an essential tool for standard Git operation. It is a counterpart to [git merge](https:\/\/www.atlassian.com\/git\/tutorials\/using-branches\/git-merge). The `git checkout` and `git merge` commands are critical tools to enabling [git workflows](https:\/\/www.atlassian.com\/git\/tutorials\/comparing-workflows).","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

8 days 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.3 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.atlassian.com/git/tutorials/using-branches/git-checkout
Last Crawled	2026-04-01 03:12:13 (8 days ago)
First Indexed	2014-09-20 14:45:30 (11 years ago)
HTTP Status Code	200
Meta Title	Git Checkout \| Atlassian Git Tutorial
Meta Description	Git branching intro. Create, list, rename, delete branches with git branch. git checkout: select which line of development you want and navigate branches
Meta Canonical	null
Boilerpipe Text	This page is an examination of the git checkout command. It will cover usage examples and edge cases. In Git terms, a "checkout" is the act of switching between different versions of a target entity. The git checkout command operates upon three distinct entities: files, commits, and branches. In addition to the definition of "checkout" the phrase "checking out" is commonly used to imply the act of executing the git checkout command. In the Undoing Changes topic, we saw how git checkout can be used to view old commits. The focus for the majority of this document will be checkout operations on branches. Checking out branches is similar to checking out old commits and files in that the working directory is updated to match the selected branch/revision; however, new changes are saved in the project history—that is, it’s not a read-only operation. Checking out branches The git checkout command lets you navigate between the branches created by git branch . Checking out a branch updates the files in the working directory to match the version stored in that branch, and it tells Git to record all new commits on that branch. Think of it as a way to select which line of development you’re working on. Having a dedicated branch for each new feature is a dramatic shift from a traditional SVN workflow. It makes it ridiculously easy to try new experiments without the fear of destroying existing functionality, and it makes it possible to work on many unrelated features at the same time. In addition, branches also facilitate several collaborative workflows. The git checkout command may occasionally be confused with git clone . The difference between the two commands is that clone works to fetch code from a remote repository, alternatively checkout works to switch between versions of code already on the local system. Usage: Existing branches Assuming the repo you're working in contains pre-existing branches, you can switch between these branches using git checkout . To find out what branches are available and what the current branch name is, execute git branch . $＞ git branch main another_branch feature_inprogress_branch $＞ git checkout feature_inprogress_branch The above example demonstrates how to view a list of available branches by executing the git branch command, and switch to a specified branch, in this case, the feature_inprogress_branch . New branches Git checkout works hand-in-hand with git branch . The git branch command can be used to create a new branch. When you want to start a new feature, you create a new branch off main using git branch new_branch . Once created you can then use git checkout new_branch to switch to that branch. Additionally, The git checkout command accepts a -b argument that acts as a convenience method which will create the new branch and immediately switch to it. You can work on multiple features in a single repository by switching between them with git checkout . git checkout -b ＜new-branch＞ The above example simultaneously creates and checks out ＜new-branch＞ . The -b option is a convenience flag that tells Git to run git branch <new-branch> before running git checkout ＜new-branch＞ . git checkout -b ＜new-branch＞＜existing-branch＞ By default git checkout -b will base the new-branch off the current HEAD . An optional additional branch parameter can be passed to git checkout . In the above example, ＜existing-branch＞ is passed which then bases new-branch off of existing-branch instead of the current HEAD . Switching branches Switching branches is a straightforward operation. Executing the following will point HEAD to the tip of ＜branchname＞. git checkout ＜branchname＞ Git tracks a history of checkout operations in the reflog. You can execute git reflog to view the history. Git checkout a remote branch When collaborating with a team it is common to utilize remote repositories. These repositories may be hosted and shared or they may be another colleague's local copy. Each remote repository will contain its own set of branches. In order to checkout a remote branch you have to first fetch the contents of the branch. git fetch --all In modern versions of Git, you can then checkout the remote branch like a local branch. git checkout ＜remotebranch＞ Older versions of Git require the creation of a new branch based on the remote . git checkout -b ＜remotebranch＞ origin/＜remotebranch＞ Additionally you can checkout a new local branch and reset it to the remote branches last commit. git checkout -b ＜branchname＞ git reset --hard origin/＜branchname＞ Detached HEADS Now that we’ve seen the three main uses of git checkout on branches, it's important to discuss the “detached HEAD” state. Remember that the HEAD is Git’s way of referring to the current snapshot. Internally, the git checkout command simply updates the HEAD to point to either the specified branch or commit. When it points to a branch, Git doesn't complain, but when you check out a commit, it switches into a “detached HEAD” state. This is a warning telling you that everything you’re doing is “detached” from the rest of your project’s development. If you were to start developing a feature while in a detached HEAD state, there would be no branch allowing you to get back to it. When you inevitably check out another branch (e.g., to merge your feature in), there would be no way to reference your feature: The point is, your development should always take place on a branch—never on a detached HEAD . This makes sure you always have a reference to your new commits. However, if you’re just looking at an old commit, it doesn’t really matter if you’re in a detached HEAD state or not. Summary This page focused on usage of the git checkout command when changing branches. In summation, git checkout , when used on branches, alters the target of the HEAD ref. It can be used to create branches, switch branches, and checkout remote branches. The git checkout command is an essential tool for standard Git operation. It is a counterpart to git merge . The git checkout and git merge commands are critical tools to enabling git workflows .
Markdown	[Skip to content](https://www.atlassian.com/git/tutorials/using-branches/git-checkout#content) - [Products](https://www.atlassian.com/git/tutorials/using-branches/git-checkout) Featured Developers Product Managers IT professionals Business Teams Leadership Teams [See all apps](https://www.atlassian.com/software) - ## Featured apps - [Jira Flexible project management](https://www.atlassian.com/software/jira) - [Confluence Knowledge, all in one place](https://www.atlassian.com/software/confluence) - [Jira Service Management Deliver service at high velocity](https://www.atlassian.com/software/jira/service-management) ## Atlassian Collections - [Supercharge teamwork seamlessly JiraConfluenceLoom](https://www.atlassian.com/collections/teamwork) - [Optimize strategy and outcomes confidently FocusTalentAlign](https://www.atlassian.com/collections/strategy) - [Deliver service at high-velocity Jira Service ManagementCustomer Service ManagementAssets](https://www.atlassian.com/collections/service) - [Ship high-quality software fast Rovo DevDXPipelinesBitbucketCompass](https://www.atlassian.com/collections/software) Powered by [Rovo AI-powered apps – driven by your team's knowledge.](https://www.atlassian.com/software/rovo) - [Jira Flexible project management](https://www.atlassian.com/software/jira) - [Bitbucket Source code and CI/CD](https://www.atlassian.com/software/bitbucket) - [Rovo Dev Agentic AI for developers](https://www.atlassian.com/software/rovo-dev) - [Pipelines Scalable CI/CD automation](https://www.atlassian.com/software/bitbucket/features/pipelines) - [DX Measure productivity and AI impact](https://www.atlassian.com/collections/software) - [Compass Software catalog for teams](https://www.atlassian.com/software/compass) - [Ship high-quality software fast Rovo DevDXPipelinesBitbucketCompass](https://www.atlassian.com/collections/software) [Rovo AI-powered apps – driven by your team's knowledge.](https://www.atlassian.com/software/rovo) - [Jira Product Discovery Capture & prioritize ideas](https://www.atlassian.com/software/jira/product-discovery) - [Jira Flexible project management](https://www.atlassian.com/software/jira) - [Confluence Knowledge, all in one place](https://www.atlassian.com/software/confluence) - [Supercharge teamwork seamlessly JiraConfluenceLoom](https://www.atlassian.com/collections/teamwork) [Rovo AI-powered apps – driven by your team's knowledge.](https://www.atlassian.com/software/rovo) - [Jira Service Management Deliver service at high velocity](https://www.atlassian.com/software/jira/service-management) - [Guard Enhanced cloud security](https://www.atlassian.com/software/guard) [Rovo AI-powered apps – driven by your team's knowledge.](https://www.atlassian.com/software/rovo) - [Jira Flexible project management](https://www.atlassian.com/software/jira) - [Confluence Knowledge, all in one place](https://www.atlassian.com/software/confluence) - [Trello Capture and organize your tasks](https://trello.com/home) - [Loom Quick, async video updates](https://www.atlassian.com/software/loom) - [Jira Service Management Deliver service at high velocity](https://www.atlassian.com/software/jira/service-management) - [Customer Service Management Customer experiences reimagined](https://www.atlassian.com/software/customer-service-management) - [Supercharge teamwork seamlessly JiraConfluenceLoom](https://www.atlassian.com/collections/teamwork) [Rovo AI-powered apps – driven by your team's knowledge.](https://www.atlassian.com/software/rovo) - [Focus Enterprise-scale strategic planning](https://www.atlassian.com/software/focus) - [Talent Knowledge workforce planning](https://www.atlassian.com/software/talent) - [Align Enterprise-wide work planning & value](https://www.atlassian.com/software/jira/align) - [Optimize strategy and outcomes confidently FocusTalentAlign](https://www.atlassian.com/collections/strategy) [Rovo AI-powered apps – driven by your team's knowledge.](https://www.atlassian.com/software/rovo) - [Solutions](https://www.atlassian.com/git/tutorials/using-branches/git-checkout) Solutions ## By Use Case - [Team collaboration](https://www.atlassian.com/collections/teamwork) - [Strategy and planning](https://www.atlassian.com/collections/strategy) - [Service management](https://www.atlassian.com/collections/service) - [Software development](https://www.atlassian.com/collections/software) ## By Team - [Software](https://www.atlassian.com/collections/software) - [Marketing](https://www.atlassian.com/teams/marketing) - [IT](https://www.atlassian.com/teams/it) - [Product](https://www.atlassian.com/software/jira/product-discovery%20) ## By Size - [Enterprise](https://www.atlassian.com/enterprise) - [Small Business](https://www.atlassian.com/software/small-business) - [Startup](https://www.atlassian.com/software/startups) - [Non-profit](https://www.atlassian.com/teams/nonprofits) ## By Industry - [Retail](https://www.atlassian.com/industries/retail) - [Telecommunications](https://www.atlassian.com/industries/telecom) - [Professional Services](https://www.atlassian.com/industries/professional-services) - [Government](https://www.atlassian.com/government) [Rovo AI-powered apps – driven by your team's knowledge.](https://www.atlassian.com/software/rovo) - [Why Atlassian?](https://www.atlassian.com/git/tutorials/using-branches/git-checkout) - [System of Work NewAtlassian's blueprint for how teams work together](https://www.atlassian.com/system-of-work) - [MarketplaceConnect thousands of apps to your Atlassian products](https://marketplace.atlassian.com/) - [CustomersCase studies & stories powered by teamwork](https://www.atlassian.com/customers) - [FedRAMPCompliant solutions for the public sector](https://www.atlassian.com/trust/compliance/resources/fedramp) - [ResilienceEnterprise-grade & highly performant infrastructure](https://www.atlassian.com/trust/resilience) - [PlatformOur deeply integrated, reliable & secure platform](https://www.atlassian.com/platform) - [Trust centerEnsure your data's security, compliance & availability](https://www.atlassian.com/trust) - [Resources](https://www.atlassian.com/git/tutorials/using-branches/git-checkout) - [Customer SupportAsk questions, report bugs & give us feedback](https://support.atlassian.com/) - [Find PartnersConsulting, training & product customization support](https://partnerdirectory.atlassian.com/) - [Atlassian AscendResources and support for your transformation](https://www.atlassian.com/migration) - [CommunityLearn, connect and grow with the Atlassian Community](https://community.atlassian.com/) ## Support ## Resources - [Enterprise](https://www.atlassian.com/enterprise) - More + Get it free Sign in Sign in - Products - Featured - Developers - Product Managers - IT professionals - Business Teams - Leadership Teams - Solutions - Why Atlassian? - Resources - [Enterprise](https://www.atlassian.com/enterprise) [Sign in](https://id.atlassian.com/login?continue=https%3A%2F%2Fwww.atlassian.com%2Fgateway%2Fapi%2Fstart%2Fauthredirect) - ## Featured apps - [Jira Flexible project management](https://www.atlassian.com/software/jira) - [Confluence Knowledge, all in one place](https://www.atlassian.com/software/confluence) - [Jira Service Management Deliver service at high velocity](https://www.atlassian.com/software/jira/service-management) ## Atlassian Collections - [Supercharge teamwork seamlessly JiraConfluenceLoom](https://www.atlassian.com/collections/teamwork) - [Optimize strategy and outcomes confidently FocusTalentAlign](https://www.atlassian.com/collections/strategy) - [Deliver service at high-velocity Jira Service ManagementCustomer Service ManagementAssets](https://www.atlassian.com/collections/service) - [Ship high-quality software fast Rovo DevDXPipelinesBitbucketCompass](https://www.atlassian.com/collections/software) Powered by [Rovo AI-powered apps – driven by your team's knowledge.](https://www.atlassian.com/software/rovo) Developers - [Jira Flexible project management](https://www.atlassian.com/software/jira) - [Bitbucket Source code and CI/CD](https://www.atlassian.com/software/bitbucket) - [Rovo Dev Agentic AI for developers](https://www.atlassian.com/software/rovo-dev) - [Pipelines Scalable CI/CD automation](https://www.atlassian.com/software/bitbucket/features/pipelines) - [DX Measure productivity and AI impact](https://www.atlassian.com/collections/software) - [Compass Software catalog for teams](https://www.atlassian.com/software/compass) - [Ship high-quality software fast Rovo DevDXPipelinesBitbucketCompass](https://www.atlassian.com/collections/software) [Rovo AI-powered apps – driven by your team's knowledge.](https://www.atlassian.com/software/rovo) Product Managers - [Jira Product Discovery Capture & prioritize ideas](https://www.atlassian.com/software/jira/product-discovery) - [Jira Flexible project management](https://www.atlassian.com/software/jira) - [Confluence Knowledge, all in one place](https://www.atlassian.com/software/confluence) - [Supercharge teamwork seamlessly JiraConfluenceLoom](https://www.atlassian.com/collections/teamwork) [Rovo AI-powered apps – driven by your team's knowledge.](https://www.atlassian.com/software/rovo) IT professionals - [Jira Service Management Deliver service at high velocity](https://www.atlassian.com/software/jira/service-management) - [Guard Enhanced cloud security](https://www.atlassian.com/software/guard) [Rovo AI-powered apps – driven by your team's knowledge.](https://www.atlassian.com/software/rovo) Business Teams - [Jira Flexible project management](https://www.atlassian.com/software/jira) - [Confluence Knowledge, all in one place](https://www.atlassian.com/software/confluence) - [Trello Capture and organize your tasks](https://trello.com/home) - [Loom Quick, async video updates](https://www.atlassian.com/software/loom) - [Jira Service Management Deliver service at high velocity](https://www.atlassian.com/software/jira/service-management) - [Customer Service Management Customer experiences reimagined](https://www.atlassian.com/software/customer-service-management) - [Supercharge teamwork seamlessly JiraConfluenceLoom](https://www.atlassian.com/collections/teamwork) [Rovo AI-powered apps – driven by your team's knowledge.](https://www.atlassian.com/software/rovo) Leadership Teams - [Focus Enterprise-scale strategic planning](https://www.atlassian.com/software/focus) - [Talent Knowledge workforce planning](https://www.atlassian.com/software/talent) - [Align Enterprise-wide work planning & value](https://www.atlassian.com/software/jira/align) - [Optimize strategy and outcomes confidently FocusTalentAlign](https://www.atlassian.com/collections/strategy) [Rovo AI-powered apps – driven by your team's knowledge.](https://www.atlassian.com/software/rovo) Solutions ## By Use Case - [Team collaboration](https://www.atlassian.com/collections/teamwork) - [Strategy and planning](https://www.atlassian.com/collections/strategy) - [Service management](https://www.atlassian.com/collections/service) - [Software development](https://www.atlassian.com/collections/software) ## By Team - [Software](https://www.atlassian.com/collections/software) - [Marketing](https://www.atlassian.com/teams/marketing) - [IT](https://www.atlassian.com/teams/it) - [Product](https://www.atlassian.com/software/jira/product-discovery%20) ## By Size - [Enterprise](https://www.atlassian.com/enterprise) - [Small Business](https://www.atlassian.com/software/small-business) - [Startup](https://www.atlassian.com/software/startups) - [Non-profit](https://www.atlassian.com/teams/nonprofits) ## By Industry - [Retail](https://www.atlassian.com/industries/retail) - [Telecommunications](https://www.atlassian.com/industries/telecom) - [Professional Services](https://www.atlassian.com/industries/professional-services) - [Government](https://www.atlassian.com/government) [Rovo AI-powered apps – driven by your team's knowledge.](https://www.atlassian.com/software/rovo) Why Atlassian [System of Work NewAtlassian's blueprint for how teams work together](https://www.atlassian.com/system-of-work) [MarketplaceConnect thousands of apps to your Atlassian products](https://marketplace.atlassian.com/) [CustomersCase studies & stories powered by teamwork](https://www.atlassian.com/customers) [FedRAMPCompliant solutions for the public sector](https://www.atlassian.com/trust/compliance/resources/fedramp) [ResilienceEnterprise-grade & highly performant infrastructure](https://www.atlassian.com/trust/resilience) [PlatformOur deeply integrated, reliable & secure platform](https://www.atlassian.com/platform) [Trust centerEnsure your data's security, compliance & availability](https://www.atlassian.com/trust) Resources [Customer SupportAsk questions, report bugs & give us feedback](https://support.atlassian.com/) [Find PartnersConsulting, training & product customization support](https://partnerdirectory.atlassian.com/) [Atlassian AscendResources and support for your transformation](https://www.atlassian.com/migration) [CommunityLearn, connect and grow with the Atlassian Community](https://community.atlassian.com/) Support - [General Inquiries](https://www.atlassian.com/company/contact/general-inquiries) - [Technical Support](https://support.atlassian.com/contact/) - [Product Advice](https://www.atlassian.com/company/contact/product-evaluator-advice) - [Pricing and Billing](https://www.atlassian.com/company/contact/purchasing-licensing) - [Partner Support](https://www.atlassian.com/partners) - [Developer Support](https://developer.atlassian.com/) - [Enterprise Support](https://www.atlassian.com/enterprise/services) - [Purchasing and Licensing](https://www.atlassian.com/licensing/purchase-licensing) Resources - [Project Management](https://www.atlassian.com/project-management) - [Project Collaboration](https://www.atlassian.com/work-management/project-collaboration) - [Agile](https://www.atlassian.com/agile) - [Team Playbook](https://www.atlassian.com/team-playbook) - [Atlassian Learning](https://community.atlassian.com/learning) - [Product Documentation](https://confluence.atlassian.com/display/ALLDOC/Atlassian+Documentation) - [Get Started](https://www.atlassian.com/get-started) [Skip to content](https://www.atlassian.com/git/tutorials/using-branches/git-checkout#content) - Products - Featured - Developers - Product Managers - IT professionals - Business Teams - Leadership Teams - Solutions - Why Atlassian? - Resources - [Enterprise](https://www.atlassian.com/enterprise) [Sign in](https://id.atlassian.com/login?continue=https%3A%2F%2Fwww.atlassian.com%2Fgateway%2Fapi%2Fstart%2Fauthredirect) - ## Featured apps - [Jira Flexible project management](https://www.atlassian.com/software/jira) - [Confluence Knowledge, all in one place](https://www.atlassian.com/software/confluence) - [Jira Service Management Deliver service at high velocity](https://www.atlassian.com/software/jira/service-management) ## Atlassian Collections - [Supercharge teamwork seamlessly JiraConfluenceLoom](https://www.atlassian.com/collections/teamwork) - [Optimize strategy and outcomes confidently FocusTalentAlign](https://www.atlassian.com/collections/strategy) - [Deliver service at high-velocity Jira Service ManagementCustomer Service ManagementAssets](https://www.atlassian.com/collections/service) - [Ship high-quality software fast Rovo DevDXPipelinesBitbucketCompass](https://www.atlassian.com/collections/software) Powered by [Rovo AI-powered apps – driven by your team's knowledge.](https://www.atlassian.com/software/rovo) Developers - [Jira Flexible project management](https://www.atlassian.com/software/jira) - [Bitbucket Source code and CI/CD](https://www.atlassian.com/software/bitbucket) - [Rovo Dev Agentic AI for developers](https://www.atlassian.com/software/rovo-dev) - [Pipelines Scalable CI/CD automation](https://www.atlassian.com/software/bitbucket/features/pipelines) - [DX Measure productivity and AI impact](https://www.atlassian.com/collections/software) - [Compass Software catalog for teams](https://www.atlassian.com/software/compass) - [Ship high-quality software fast Rovo DevDXPipelinesBitbucketCompass](https://www.atlassian.com/collections/software) [Rovo AI-powered apps – driven by your team's knowledge.](https://www.atlassian.com/software/rovo) Product Managers - [Jira Product Discovery Capture & prioritize ideas](https://www.atlassian.com/software/jira/product-discovery) - [Jira Flexible project management](https://www.atlassian.com/software/jira) - [Confluence Knowledge, all in one place](https://www.atlassian.com/software/confluence) - [Supercharge teamwork seamlessly JiraConfluenceLoom](https://www.atlassian.com/collections/teamwork) [Rovo AI-powered apps – driven by your team's knowledge.](https://www.atlassian.com/software/rovo) IT professionals - [Jira Service Management Deliver service at high velocity](https://www.atlassian.com/software/jira/service-management) - [Guard Enhanced cloud security](https://www.atlassian.com/software/guard) [Rovo AI-powered apps – driven by your team's knowledge.](https://www.atlassian.com/software/rovo) Business Teams - [Jira Flexible project management](https://www.atlassian.com/software/jira) - [Confluence Knowledge, all in one place](https://www.atlassian.com/software/confluence) - [Trello Capture and organize your tasks](https://trello.com/home) - [Loom Quick, async video updates](https://www.atlassian.com/software/loom) - [Jira Service Management Deliver service at high velocity](https://www.atlassian.com/software/jira/service-management) - [Customer Service Management Customer experiences reimagined](https://www.atlassian.com/software/customer-service-management) - [Supercharge teamwork seamlessly JiraConfluenceLoom](https://www.atlassian.com/collections/teamwork) [Rovo AI-powered apps – driven by your team's knowledge.](https://www.atlassian.com/software/rovo) Leadership Teams - [Focus Enterprise-scale strategic planning](https://www.atlassian.com/software/focus) - [Talent Knowledge workforce planning](https://www.atlassian.com/software/talent) - [Align Enterprise-wide work planning & value](https://www.atlassian.com/software/jira/align) - [Optimize strategy and outcomes confidently FocusTalentAlign](https://www.atlassian.com/collections/strategy) [Rovo AI-powered apps – driven by your team's knowledge.](https://www.atlassian.com/software/rovo) Solutions ## By Use Case - [Team collaboration](https://www.atlassian.com/collections/teamwork) - [Strategy and planning](https://www.atlassian.com/collections/strategy) - [Service management](https://www.atlassian.com/collections/service) - [Software development](https://www.atlassian.com/collections/software) ## By Team - [Software](https://www.atlassian.com/collections/software) - [Marketing](https://www.atlassian.com/teams/marketing) - [IT](https://www.atlassian.com/teams/it) - [Product](https://www.atlassian.com/software/jira/product-discovery%20) ## By Size - [Enterprise](https://www.atlassian.com/enterprise) - [Small Business](https://www.atlassian.com/software/small-business) - [Startup](https://www.atlassian.com/software/startups) - [Non-profit](https://www.atlassian.com/teams/nonprofits) ## By Industry - [Retail](https://www.atlassian.com/industries/retail) - [Telecommunications](https://www.atlassian.com/industries/telecom) - [Professional Services](https://www.atlassian.com/industries/professional-services) - [Government](https://www.atlassian.com/government) [Rovo AI-powered apps – driven by your team's knowledge.](https://www.atlassian.com/software/rovo) Why Atlassian [System of Work NewAtlassian's blueprint for how teams work together](https://www.atlassian.com/system-of-work) [MarketplaceConnect thousands of apps to your Atlassian products](https://marketplace.atlassian.com/) [CustomersCase studies & stories powered by teamwork](https://www.atlassian.com/customers) [FedRAMPCompliant solutions for the public sector](https://www.atlassian.com/trust/compliance/resources/fedramp) [ResilienceEnterprise-grade & highly performant infrastructure](https://www.atlassian.com/trust/resilience) [PlatformOur deeply integrated, reliable & secure platform](https://www.atlassian.com/platform) [Trust centerEnsure your data's security, compliance & availability](https://www.atlassian.com/trust) Resources [Customer SupportAsk questions, report bugs & give us feedback](https://support.atlassian.com/) [Find PartnersConsulting, training & product customization support](https://partnerdirectory.atlassian.com/) [Atlassian AscendResources and support for your transformation](https://www.atlassian.com/migration) [CommunityLearn, connect and grow with the Atlassian Community](https://community.atlassian.com/) Support - [General Inquiries](https://www.atlassian.com/company/contact/general-inquiries) - [Technical Support](https://support.atlassian.com/contact/) - [Product Advice](https://www.atlassian.com/company/contact/product-evaluator-advice) - [Pricing and Billing](https://www.atlassian.com/company/contact/purchasing-licensing) - [Partner Support](https://www.atlassian.com/partners) - [Developer Support](https://developer.atlassian.com/) - [Enterprise Support](https://www.atlassian.com/enterprise/services) - [Purchasing and Licensing](https://www.atlassian.com/licensing/purchase-licensing) Resources - [Project Management](https://www.atlassian.com/project-management) - [Project Collaboration](https://www.atlassian.com/work-management/project-collaboration) - [Agile](https://www.atlassian.com/agile) - [Team Playbook](https://www.atlassian.com/team-playbook) - [Atlassian Learning](https://community.atlassian.com/learning) - [Product Documentation](https://confluence.atlassian.com/display/ALLDOC/Atlassian+Documentation) - [Get Started](https://www.atlassian.com/get-started) Git topics - Learn Git - [Git commands](https://www.atlassian.com/git/glossary) - [Learn Git with Bitbucket Cloud](https://www.atlassian.com/git/tutorials/learn-git-with-bitbucket-cloud) - [Learn about code review in Bitbucket Cloud](https://www.atlassian.com/git/tutorials/learn-about-code-review-in-bitbucket-cloud) - [Learn Branching with Bitbucket Cloud](https://www.atlassian.com/git/tutorials/learn-branching-with-bitbucket-cloud) - [Learn Undoing Changes with Bitbucket Cloud](https://www.atlassian.com/git/tutorials/learn-undoing-changes-with-bitbucket) - Beginner - [What is version control](https://www.atlassian.com/git/tutorials/what-is-version-control) - [Source Code Management](https://www.atlassian.com/git/tutorials/source-code-management) - [What is Git](https://www.atlassian.com/git/tutorials/what-is-git) - [Why Git for your organization](https://www.atlassian.com/git/tutorials/why-git) - [Install Git](https://www.atlassian.com/git/tutorials/install-git) - [Git SSH](https://www.atlassian.com/git/tutorials/git-ssh) - [Git archive](https://www.atlassian.com/git/tutorials/export-git-archive) - [GitOps](https://www.atlassian.com/git/tutorials/gitops) - [Git cheat sheet](https://www.atlassian.com/git/tutorials/atlassian-git-cheatsheet) - Getting started - Setting up a repository - [Overview](https://www.atlassian.com/git/tutorials/setting-up-a-repository) - [git init](https://www.atlassian.com/git/tutorials/setting-up-a-repository/git-init) - [git clone](https://www.atlassian.com/git/tutorials/setting-up-a-repository/git-clone) - [git config](https://www.atlassian.com/git/tutorials/setting-up-a-repository/git-config) - [git alias](https://www.atlassian.com/git/tutorials/git-alias) - Saving changes (Git add) - [Overview](https://www.atlassian.com/git/tutorials/saving-changes) - [git commit](https://www.atlassian.com/git/tutorials/saving-changes/git-commit) - [git diff](https://www.atlassian.com/git/tutorials/saving-changes/git-diff) - [git stash](https://www.atlassian.com/git/tutorials/saving-changes/git-stash) - [.gitignore](https://www.atlassian.com/git/tutorials/saving-changes/gitignore) - Inspecting a repository - [Overview](https://www.atlassian.com/git/tutorials/inspecting-a-repository) - [git tag](https://www.atlassian.com/git/tutorials/inspecting-a-repository/git-tag) - [git blame](https://www.atlassian.com/git/tutorials/inspecting-a-repository/git-blame) - Undoing changes - [Overview](https://www.atlassian.com/git/tutorials/undoing-changes) - [git clean](https://www.atlassian.com/git/tutorials/undoing-changes/git-clean) - [git revert](https://www.atlassian.com/git/tutorials/undoing-changes/git-revert) - [git reset](https://www.atlassian.com/git/tutorials/undoing-changes/git-reset) - [git rm](https://www.atlassian.com/git/tutorials/undoing-changes/git-rm) - Rewriting history - [Overview](https://www.atlassian.com/git/tutorials/rewriting-history) - [git rebase](https://www.atlassian.com/git/tutorials/rewriting-history/git-rebase) - [git reflog](https://www.atlassian.com/git/tutorials/rewriting-history/git-reflog) - Collaborating workflows - Syncing (git remote) - [Overview](https://www.atlassian.com/git/tutorials/syncing) - [git fetch](https://www.atlassian.com/git/tutorials/syncing/git-fetch) - [git push](https://www.atlassian.com/git/tutorials/syncing/git-push) - [git pull](https://www.atlassian.com/git/tutorials/syncing/git-pull) - [Making a Pull Request](https://www.atlassian.com/git/tutorials/making-a-pull-request) - Using Branches (Git branch) - [Overview](https://www.atlassian.com/git/tutorials/using-branches) - [git checkout](https://www.atlassian.com/git/tutorials/using-branches/git-checkout) - [git merge](https://www.atlassian.com/git/tutorials/using-branches/git-merge) - [Merge conflicts](https://www.atlassian.com/git/tutorials/using-branches/merge-conflicts) - [Merge strategies](https://www.atlassian.com/git/tutorials/using-branches/merge-strategy) - Comparing Workflows - [Overview](https://www.atlassian.com/git/tutorials/comparing-workflows) - [Feature Branch Workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/feature-branch-workflow) - [Gitflow Workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow) - [Forking Workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/forking-workflow) - Migrating to Git - [SVN to Git - prepping for the migration](https://www.atlassian.com/git/tutorials/svn-to-git-prepping-your-team-migration) - Migrate to Git from SVN - [Overview](https://www.atlassian.com/git/tutorials/migrating-overview) - [Prepare](https://www.atlassian.com/git/tutorials/migrating-prepare) - [Convert](https://www.atlassian.com/git/tutorials/migrating-convert) - [Synchronize](https://www.atlassian.com/git/tutorials/migrating-synchronize) - [Share](https://www.atlassian.com/git/tutorials/migrating-share) - [Migrate](https://www.atlassian.com/git/tutorials/migrating-migrate) - [Perforce to Git - why to make the move](https://www.atlassian.com/git/tutorials/perforce-git) - [Migrating from Perforce to Git](https://www.atlassian.com/git/tutorials/perforce-git-migration) - [Working with Git and Perforce: integration workflow](https://www.atlassian.com/git/tutorials/git-p4) - [How to move a Git repository with history](https://www.atlassian.com/git/tutorials/git-move-repository) - Advanced Tips - [Overview](https://www.atlassian.com/git/tutorials/advanced-overview) - [Merging vs. Rebasing](https://www.atlassian.com/git/tutorials/merging-vs-rebasing) - [Reset, Checkout, and Revert](https://www.atlassian.com/git/tutorials/resetting-checking-out-and-reverting) - [Advanced Git log](https://www.atlassian.com/git/tutorials/git-log) - [Git Hooks](https://www.atlassian.com/git/tutorials/git-hooks) - [Refs and the Reflog](https://www.atlassian.com/git/tutorials/refs-and-the-reflog) - [Git submodules](https://www.atlassian.com/git/tutorials/git-submodule) - [Git subtree](https://www.atlassian.com/git/tutorials/git-subtree) - [Large repositories in Git](https://www.atlassian.com/git/tutorials/big-repositories) - [Git LFS](https://www.atlassian.com/git/tutorials/git-lfs) - [Git gc](https://www.atlassian.com/git/tutorials/git-gc) - [Git prune](https://www.atlassian.com/git/tutorials/git-prune) - [Git bash](https://www.atlassian.com/git/tutorials/git-bash) - [How to store dotfiles](https://www.atlassian.com/git/tutorials/dotfiles) - [Git cherry pick](https://www.atlassian.com/git/tutorials/cherry-pick) - [GitK](https://www.atlassian.com/git/tutorials/gitk) - [Git-show](https://www.atlassian.com/git/tutorials/git-show) - Articles - [Dealing with Maven dependencies when switching to Git](https://www.atlassian.com/git/articles/maven-dependencies-versions-merging) - [Pull request proficiency: Fetching abilities unlocked\!](https://www.atlassian.com/git/articles/pull-request-proficiency-fetching-abilities-unlocked) - [Git and project dependencies](https://www.atlassian.com/git/articles/git-and-project-dependencies) - [Git or SVN? How Nuance Healthcare Chose a Git Branching Model](https://www.atlassian.com/git/articles/git-or-svn-git-branching-model) - [Git Forks And Upstreams: How-to and a cool tip](https://www.atlassian.com/git/tutorials/git-forks-and-upstreams) - [Core concept, workflows and tips](https://www.atlassian.com/git/articles/core-concept-workflows-and-tips) Git topics - Learn Git - [Git commands](https://www.atlassian.com/git/glossary) - [Learn Git with Bitbucket Cloud](https://www.atlassian.com/git/tutorials/learn-git-with-bitbucket-cloud) - [Learn about code review in Bitbucket Cloud](https://www.atlassian.com/git/tutorials/learn-about-code-review-in-bitbucket-cloud) - [Learn Branching with Bitbucket Cloud](https://www.atlassian.com/git/tutorials/learn-branching-with-bitbucket-cloud) - [Learn Undoing Changes with Bitbucket Cloud](https://www.atlassian.com/git/tutorials/learn-undoing-changes-with-bitbucket) - Beginner - [What is version control](https://www.atlassian.com/git/tutorials/what-is-version-control) - [Source Code Management](https://www.atlassian.com/git/tutorials/source-code-management) - [What is Git](https://www.atlassian.com/git/tutorials/what-is-git) - [Why Git for your organization](https://www.atlassian.com/git/tutorials/why-git) - [Install Git](https://www.atlassian.com/git/tutorials/install-git) - [Git SSH](https://www.atlassian.com/git/tutorials/git-ssh) - [Git archive](https://www.atlassian.com/git/tutorials/export-git-archive) - [GitOps](https://www.atlassian.com/git/tutorials/gitops) - [Git cheat sheet](https://www.atlassian.com/git/tutorials/atlassian-git-cheatsheet) - Getting started - Setting up a repository - [Overview](https://www.atlassian.com/git/tutorials/setting-up-a-repository) - [git init](https://www.atlassian.com/git/tutorials/setting-up-a-repository/git-init) - [git clone](https://www.atlassian.com/git/tutorials/setting-up-a-repository/git-clone) - [git config](https://www.atlassian.com/git/tutorials/setting-up-a-repository/git-config) - [git alias](https://www.atlassian.com/git/tutorials/git-alias) - Saving changes (Git add) - [Overview](https://www.atlassian.com/git/tutorials/saving-changes) - [git commit](https://www.atlassian.com/git/tutorials/saving-changes/git-commit) - [git diff](https://www.atlassian.com/git/tutorials/saving-changes/git-diff) - [git stash](https://www.atlassian.com/git/tutorials/saving-changes/git-stash) - [.gitignore](https://www.atlassian.com/git/tutorials/saving-changes/gitignore) - Inspecting a repository - [Overview](https://www.atlassian.com/git/tutorials/inspecting-a-repository) - [git tag](https://www.atlassian.com/git/tutorials/inspecting-a-repository/git-tag) - [git blame](https://www.atlassian.com/git/tutorials/inspecting-a-repository/git-blame) - Undoing changes - [Overview](https://www.atlassian.com/git/tutorials/undoing-changes) - [git clean](https://www.atlassian.com/git/tutorials/undoing-changes/git-clean) - [git revert](https://www.atlassian.com/git/tutorials/undoing-changes/git-revert) - [git reset](https://www.atlassian.com/git/tutorials/undoing-changes/git-reset) - [git rm](https://www.atlassian.com/git/tutorials/undoing-changes/git-rm) - Rewriting history - [Overview](https://www.atlassian.com/git/tutorials/rewriting-history) - [git rebase](https://www.atlassian.com/git/tutorials/rewriting-history/git-rebase) - [git reflog](https://www.atlassian.com/git/tutorials/rewriting-history/git-reflog) - Collaborating workflows - Syncing (git remote) - [Overview](https://www.atlassian.com/git/tutorials/syncing) - [git fetch](https://www.atlassian.com/git/tutorials/syncing/git-fetch) - [git push](https://www.atlassian.com/git/tutorials/syncing/git-push) - [git pull](https://www.atlassian.com/git/tutorials/syncing/git-pull) - [Making a Pull Request](https://www.atlassian.com/git/tutorials/making-a-pull-request) - Using Branches (Git branch) - [Overview](https://www.atlassian.com/git/tutorials/using-branches) - [git checkout](https://www.atlassian.com/git/tutorials/using-branches/git-checkout) - [git merge](https://www.atlassian.com/git/tutorials/using-branches/git-merge) - [Merge conflicts](https://www.atlassian.com/git/tutorials/using-branches/merge-conflicts) - [Merge strategies](https://www.atlassian.com/git/tutorials/using-branches/merge-strategy) - Comparing Workflows - [Overview](https://www.atlassian.com/git/tutorials/comparing-workflows) - [Feature Branch Workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/feature-branch-workflow) - [Gitflow Workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow) - [Forking Workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/forking-workflow) - Migrating to Git - [SVN to Git - prepping for the migration](https://www.atlassian.com/git/tutorials/svn-to-git-prepping-your-team-migration) - Migrate to Git from SVN - [Overview](https://www.atlassian.com/git/tutorials/migrating-overview) - [Prepare](https://www.atlassian.com/git/tutorials/migrating-prepare) - [Convert](https://www.atlassian.com/git/tutorials/migrating-convert) - [Synchronize](https://www.atlassian.com/git/tutorials/migrating-synchronize) - [Share](https://www.atlassian.com/git/tutorials/migrating-share) - [Migrate](https://www.atlassian.com/git/tutorials/migrating-migrate) - [Perforce to Git - why to make the move](https://www.atlassian.com/git/tutorials/perforce-git) - [Migrating from Perforce to Git](https://www.atlassian.com/git/tutorials/perforce-git-migration) - [Working with Git and Perforce: integration workflow](https://www.atlassian.com/git/tutorials/git-p4) - [How to move a Git repository with history](https://www.atlassian.com/git/tutorials/git-move-repository) - Advanced Tips - [Overview](https://www.atlassian.com/git/tutorials/advanced-overview) - [Merging vs. Rebasing](https://www.atlassian.com/git/tutorials/merging-vs-rebasing) - [Reset, Checkout, and Revert](https://www.atlassian.com/git/tutorials/resetting-checking-out-and-reverting) - [Advanced Git log](https://www.atlassian.com/git/tutorials/git-log) - [Git Hooks](https://www.atlassian.com/git/tutorials/git-hooks) - [Refs and the Reflog](https://www.atlassian.com/git/tutorials/refs-and-the-reflog) - [Git submodules](https://www.atlassian.com/git/tutorials/git-submodule) - [Git subtree](https://www.atlassian.com/git/tutorials/git-subtree) - [Large repositories in Git](https://www.atlassian.com/git/tutorials/big-repositories) - [Git LFS](https://www.atlassian.com/git/tutorials/git-lfs) - [Git gc](https://www.atlassian.com/git/tutorials/git-gc) - [Git prune](https://www.atlassian.com/git/tutorials/git-prune) - [Git bash](https://www.atlassian.com/git/tutorials/git-bash) - [How to store dotfiles](https://www.atlassian.com/git/tutorials/dotfiles) - [Git cherry pick](https://www.atlassian.com/git/tutorials/cherry-pick) - [GitK](https://www.atlassian.com/git/tutorials/gitk) - [Git-show](https://www.atlassian.com/git/tutorials/git-show) - Articles - [Dealing with Maven dependencies when switching to Git](https://www.atlassian.com/git/articles/maven-dependencies-versions-merging) - [Pull request proficiency: Fetching abilities unlocked\!](https://www.atlassian.com/git/articles/pull-request-proficiency-fetching-abilities-unlocked) - [Git and project dependencies](https://www.atlassian.com/git/articles/git-and-project-dependencies) - [Git or SVN? How Nuance Healthcare Chose a Git Branching Model](https://www.atlassian.com/git/articles/git-or-svn-git-branching-model) - [Git Forks And Upstreams: How-to and a cool tip](https://www.atlassian.com/git/tutorials/git-forks-and-upstreams) - [Core concept, workflows and tips](https://www.atlassian.com/git/articles/core-concept-workflows-and-tips) Git topics - Learn Git - [Git commands](https://www.atlassian.com/git/glossary) - [Learn Git with Bitbucket Cloud](https://www.atlassian.com/git/tutorials/learn-git-with-bitbucket-cloud) - [Learn about code review in Bitbucket Cloud](https://www.atlassian.com/git/tutorials/learn-about-code-review-in-bitbucket-cloud) - [Learn Branching with Bitbucket Cloud](https://www.atlassian.com/git/tutorials/learn-branching-with-bitbucket-cloud) - [Learn Undoing Changes with Bitbucket Cloud](https://www.atlassian.com/git/tutorials/learn-undoing-changes-with-bitbucket) - Beginner - [What is version control](https://www.atlassian.com/git/tutorials/what-is-version-control) - [Source Code Management](https://www.atlassian.com/git/tutorials/source-code-management) - [What is Git](https://www.atlassian.com/git/tutorials/what-is-git) - [Why Git for your organization](https://www.atlassian.com/git/tutorials/why-git) - [Install Git](https://www.atlassian.com/git/tutorials/install-git) - [Git SSH](https://www.atlassian.com/git/tutorials/git-ssh) - [Git archive](https://www.atlassian.com/git/tutorials/export-git-archive) - [GitOps](https://www.atlassian.com/git/tutorials/gitops) - [Git cheat sheet](https://www.atlassian.com/git/tutorials/atlassian-git-cheatsheet) - Getting started - Setting up a repository - [Overview](https://www.atlassian.com/git/tutorials/setting-up-a-repository) - [git init](https://www.atlassian.com/git/tutorials/setting-up-a-repository/git-init) - [git clone](https://www.atlassian.com/git/tutorials/setting-up-a-repository/git-clone) - [git config](https://www.atlassian.com/git/tutorials/setting-up-a-repository/git-config) - [git alias](https://www.atlassian.com/git/tutorials/git-alias) - Saving changes (Git add) - [Overview](https://www.atlassian.com/git/tutorials/saving-changes) - [git commit](https://www.atlassian.com/git/tutorials/saving-changes/git-commit) - [git diff](https://www.atlassian.com/git/tutorials/saving-changes/git-diff) - [git stash](https://www.atlassian.com/git/tutorials/saving-changes/git-stash) - [.gitignore](https://www.atlassian.com/git/tutorials/saving-changes/gitignore) - Inspecting a repository - [Overview](https://www.atlassian.com/git/tutorials/inspecting-a-repository) - [git tag](https://www.atlassian.com/git/tutorials/inspecting-a-repository/git-tag) - [git blame](https://www.atlassian.com/git/tutorials/inspecting-a-repository/git-blame) - Undoing changes - [Overview](https://www.atlassian.com/git/tutorials/undoing-changes) - [git clean](https://www.atlassian.com/git/tutorials/undoing-changes/git-clean) - [git revert](https://www.atlassian.com/git/tutorials/undoing-changes/git-revert) - [git reset](https://www.atlassian.com/git/tutorials/undoing-changes/git-reset) - [git rm](https://www.atlassian.com/git/tutorials/undoing-changes/git-rm) - Rewriting history - [Overview](https://www.atlassian.com/git/tutorials/rewriting-history) - [git rebase](https://www.atlassian.com/git/tutorials/rewriting-history/git-rebase) - [git reflog](https://www.atlassian.com/git/tutorials/rewriting-history/git-reflog) - Collaborating workflows - Syncing (git remote) - [Overview](https://www.atlassian.com/git/tutorials/syncing) - [git fetch](https://www.atlassian.com/git/tutorials/syncing/git-fetch) - [git push](https://www.atlassian.com/git/tutorials/syncing/git-push) - [git pull](https://www.atlassian.com/git/tutorials/syncing/git-pull) - [Making a Pull Request](https://www.atlassian.com/git/tutorials/making-a-pull-request) - Using Branches (Git branch) - [Overview](https://www.atlassian.com/git/tutorials/using-branches) - [git checkout](https://www.atlassian.com/git/tutorials/using-branches/git-checkout) - [git merge](https://www.atlassian.com/git/tutorials/using-branches/git-merge) - [Merge conflicts](https://www.atlassian.com/git/tutorials/using-branches/merge-conflicts) - [Merge strategies](https://www.atlassian.com/git/tutorials/using-branches/merge-strategy) - Comparing Workflows - [Overview](https://www.atlassian.com/git/tutorials/comparing-workflows) - [Feature Branch Workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/feature-branch-workflow) - [Gitflow Workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow) - [Forking Workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/forking-workflow) - Migrating to Git - [SVN to Git - prepping for the migration](https://www.atlassian.com/git/tutorials/svn-to-git-prepping-your-team-migration) - Migrate to Git from SVN - [Overview](https://www.atlassian.com/git/tutorials/migrating-overview) - [Prepare](https://www.atlassian.com/git/tutorials/migrating-prepare) - [Convert](https://www.atlassian.com/git/tutorials/migrating-convert) - [Synchronize](https://www.atlassian.com/git/tutorials/migrating-synchronize) - [Share](https://www.atlassian.com/git/tutorials/migrating-share) - [Migrate](https://www.atlassian.com/git/tutorials/migrating-migrate) - [Perforce to Git - why to make the move](https://www.atlassian.com/git/tutorials/perforce-git) - [Migrating from Perforce to Git](https://www.atlassian.com/git/tutorials/perforce-git-migration) - [Working with Git and Perforce: integration workflow](https://www.atlassian.com/git/tutorials/git-p4) - [How to move a Git repository with history](https://www.atlassian.com/git/tutorials/git-move-repository) - Advanced Tips - [Overview](https://www.atlassian.com/git/tutorials/advanced-overview) - [Merging vs. Rebasing](https://www.atlassian.com/git/tutorials/merging-vs-rebasing) - [Reset, Checkout, and Revert](https://www.atlassian.com/git/tutorials/resetting-checking-out-and-reverting) - [Advanced Git log](https://www.atlassian.com/git/tutorials/git-log) - [Git Hooks](https://www.atlassian.com/git/tutorials/git-hooks) - [Refs and the Reflog](https://www.atlassian.com/git/tutorials/refs-and-the-reflog) - [Git submodules](https://www.atlassian.com/git/tutorials/git-submodule) - [Git subtree](https://www.atlassian.com/git/tutorials/git-subtree) - [Large repositories in Git](https://www.atlassian.com/git/tutorials/big-repositories) - [Git LFS](https://www.atlassian.com/git/tutorials/git-lfs) - [Git gc](https://www.atlassian.com/git/tutorials/git-gc) - [Git prune](https://www.atlassian.com/git/tutorials/git-prune) - [Git bash](https://www.atlassian.com/git/tutorials/git-bash) - [How to store dotfiles](https://www.atlassian.com/git/tutorials/dotfiles) - [Git cherry pick](https://www.atlassian.com/git/tutorials/cherry-pick) - [GitK](https://www.atlassian.com/git/tutorials/gitk) - [Git-show](https://www.atlassian.com/git/tutorials/git-show) - Articles - [Dealing with Maven dependencies when switching to Git](https://www.atlassian.com/git/articles/maven-dependencies-versions-merging) - [Pull request proficiency: Fetching abilities unlocked\!](https://www.atlassian.com/git/articles/pull-request-proficiency-fetching-abilities-unlocked) - [Git and project dependencies](https://www.atlassian.com/git/articles/git-and-project-dependencies) - [Git or SVN? How Nuance Healthcare Chose a Git Branching Model](https://www.atlassian.com/git/articles/git-or-svn-git-branching-model) - [Git Forks And Upstreams: How-to and a cool tip](https://www.atlassian.com/git/tutorials/git-forks-and-upstreams) - [Core concept, workflows and tips](https://www.atlassian.com/git/articles/core-concept-workflows-and-tips) Git topics - Learn Git - [Git commands](https://www.atlassian.com/git/glossary) - [Learn Git with Bitbucket Cloud](https://www.atlassian.com/git/tutorials/learn-git-with-bitbucket-cloud) - [Learn about code review in Bitbucket Cloud](https://www.atlassian.com/git/tutorials/learn-about-code-review-in-bitbucket-cloud) - [Learn Branching with Bitbucket Cloud](https://www.atlassian.com/git/tutorials/learn-branching-with-bitbucket-cloud) - [Learn Undoing Changes with Bitbucket Cloud](https://www.atlassian.com/git/tutorials/learn-undoing-changes-with-bitbucket) - Beginner - [What is version control](https://www.atlassian.com/git/tutorials/what-is-version-control) - [Source Code Management](https://www.atlassian.com/git/tutorials/source-code-management) - [What is Git](https://www.atlassian.com/git/tutorials/what-is-git) - [Why Git for your organization](https://www.atlassian.com/git/tutorials/why-git) - [Install Git](https://www.atlassian.com/git/tutorials/install-git) - [Git SSH](https://www.atlassian.com/git/tutorials/git-ssh) - [Git archive](https://www.atlassian.com/git/tutorials/export-git-archive) - [GitOps](https://www.atlassian.com/git/tutorials/gitops) - [Git cheat sheet](https://www.atlassian.com/git/tutorials/atlassian-git-cheatsheet) - Getting started - Setting up a repository - [Overview](https://www.atlassian.com/git/tutorials/setting-up-a-repository) - [git init](https://www.atlassian.com/git/tutorials/setting-up-a-repository/git-init) - [git clone](https://www.atlassian.com/git/tutorials/setting-up-a-repository/git-clone) - [git config](https://www.atlassian.com/git/tutorials/setting-up-a-repository/git-config) - [git alias](https://www.atlassian.com/git/tutorials/git-alias) - Saving changes (Git add) - [Overview](https://www.atlassian.com/git/tutorials/saving-changes) - [git commit](https://www.atlassian.com/git/tutorials/saving-changes/git-commit) - [git diff](https://www.atlassian.com/git/tutorials/saving-changes/git-diff) - [git stash](https://www.atlassian.com/git/tutorials/saving-changes/git-stash) - [.gitignore](https://www.atlassian.com/git/tutorials/saving-changes/gitignore) - Inspecting a repository - [Overview](https://www.atlassian.com/git/tutorials/inspecting-a-repository) - [git tag](https://www.atlassian.com/git/tutorials/inspecting-a-repository/git-tag) - [git blame](https://www.atlassian.com/git/tutorials/inspecting-a-repository/git-blame) - Undoing changes - [Overview](https://www.atlassian.com/git/tutorials/undoing-changes) - [git clean](https://www.atlassian.com/git/tutorials/undoing-changes/git-clean) - [git revert](https://www.atlassian.com/git/tutorials/undoing-changes/git-revert) - [git reset](https://www.atlassian.com/git/tutorials/undoing-changes/git-reset) - [git rm](https://www.atlassian.com/git/tutorials/undoing-changes/git-rm) - Rewriting history - [Overview](https://www.atlassian.com/git/tutorials/rewriting-history) - [git rebase](https://www.atlassian.com/git/tutorials/rewriting-history/git-rebase) - [git reflog](https://www.atlassian.com/git/tutorials/rewriting-history/git-reflog) - Collaborating workflows - Syncing (git remote) - [Overview](https://www.atlassian.com/git/tutorials/syncing) - [git fetch](https://www.atlassian.com/git/tutorials/syncing/git-fetch) - [git push](https://www.atlassian.com/git/tutorials/syncing/git-push) - [git pull](https://www.atlassian.com/git/tutorials/syncing/git-pull) - [Making a Pull Request](https://www.atlassian.com/git/tutorials/making-a-pull-request) - Using Branches (Git branch) - [Overview](https://www.atlassian.com/git/tutorials/using-branches) - [git checkout](https://www.atlassian.com/git/tutorials/using-branches/git-checkout) - [git merge](https://www.atlassian.com/git/tutorials/using-branches/git-merge) - [Merge conflicts](https://www.atlassian.com/git/tutorials/using-branches/merge-conflicts) - [Merge strategies](https://www.atlassian.com/git/tutorials/using-branches/merge-strategy) - Comparing Workflows - [Overview](https://www.atlassian.com/git/tutorials/comparing-workflows) - [Feature Branch Workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/feature-branch-workflow) - [Gitflow Workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow) - [Forking Workflow](https://www.atlassian.com/git/tutorials/comparing-workflows/forking-workflow) - Migrating to Git - [SVN to Git - prepping for the migration](https://www.atlassian.com/git/tutorials/svn-to-git-prepping-your-team-migration) - Migrate to Git from SVN - [Overview](https://www.atlassian.com/git/tutorials/migrating-overview) - [Prepare](https://www.atlassian.com/git/tutorials/migrating-prepare) - [Convert](https://www.atlassian.com/git/tutorials/migrating-convert) - [Synchronize](https://www.atlassian.com/git/tutorials/migrating-synchronize) - [Share](https://www.atlassian.com/git/tutorials/migrating-share) - [Migrate](https://www.atlassian.com/git/tutorials/migrating-migrate) - [Perforce to Git - why to make the move](https://www.atlassian.com/git/tutorials/perforce-git) - [Migrating from Perforce to Git](https://www.atlassian.com/git/tutorials/perforce-git-migration) - [Working with Git and Perforce: integration workflow](https://www.atlassian.com/git/tutorials/git-p4) - [How to move a Git repository with history](https://www.atlassian.com/git/tutorials/git-move-repository) - Advanced Tips - [Overview](https://www.atlassian.com/git/tutorials/advanced-overview) - [Merging vs. Rebasing](https://www.atlassian.com/git/tutorials/merging-vs-rebasing) - [Reset, Checkout, and Revert](https://www.atlassian.com/git/tutorials/resetting-checking-out-and-reverting) - [Advanced Git log](https://www.atlassian.com/git/tutorials/git-log) - [Git Hooks](https://www.atlassian.com/git/tutorials/git-hooks) - [Refs and the Reflog](https://www.atlassian.com/git/tutorials/refs-and-the-reflog) - [Git submodules](https://www.atlassian.com/git/tutorials/git-submodule) - [Git subtree](https://www.atlassian.com/git/tutorials/git-subtree) - [Large repositories in Git](https://www.atlassian.com/git/tutorials/big-repositories) - [Git LFS](https://www.atlassian.com/git/tutorials/git-lfs) - [Git gc](https://www.atlassian.com/git/tutorials/git-gc) - [Git prune](https://www.atlassian.com/git/tutorials/git-prune) - [Git bash](https://www.atlassian.com/git/tutorials/git-bash) - [How to store dotfiles](https://www.atlassian.com/git/tutorials/dotfiles) - [Git cherry pick](https://www.atlassian.com/git/tutorials/cherry-pick) - [GitK](https://www.atlassian.com/git/tutorials/gitk) - [Git-show](https://www.atlassian.com/git/tutorials/git-show) - Articles - [Dealing with Maven dependencies when switching to Git](https://www.atlassian.com/git/articles/maven-dependencies-versions-merging) - [Pull request proficiency: Fetching abilities unlocked\!](https://www.atlassian.com/git/articles/pull-request-proficiency-fetching-abilities-unlocked) - [Git and project dependencies](https://www.atlassian.com/git/articles/git-and-project-dependencies) - [Git or SVN? How Nuance Healthcare Chose a Git Branching Model](https://www.atlassian.com/git/articles/git-or-svn-git-branching-model) - [Git Forks And Upstreams: How-to and a cool tip](https://www.atlassian.com/git/tutorials/git-forks-and-upstreams) - [Core concept, workflows and tips](https://www.atlassian.com/git/articles/core-concept-workflows-and-tips) # Git checkout This page is an examination of the `git checkout` command. It will cover usage examples and edge cases. In Git terms, a "checkout" is the act of switching between different versions of a target entity. The `git checkout` command operates upon three distinct entities: files, commits, and branches. In addition to the definition of "checkout" the phrase "checking out" is commonly used to imply the act of executing the `git checkout` command. In the [Undoing Changes](https://www.atlassian.com/git/tutorials/undoing-changes) topic, we saw how `git checkout` can be used to view old commits. The focus for the majority of this document will be checkout operations on branches. Checking out branches is similar to checking out old commits and files in that the working directory is updated to match the selected branch/revision; however, new changes are saved in the project history—that is, it’s not a read-only operation. ## Checking out branches The `git checkout` command lets you navigate between the branches created by `git branch`. Checking out a branch updates the files in the working directory to match the version stored in that branch, and it tells Git to record all new commits on that branch. Think of it as a way to select which line of development you’re working on. Having a dedicated branch for each new feature is a dramatic shift from a traditional SVN workflow. It makes it ridiculously easy to try new experiments without the fear of destroying existing functionality, and it makes it possible to work on many unrelated features at the same time. In addition, branches also facilitate several collaborative workflows. The `git checkout` command may occasionally be confused with `git clone`. The difference between the two commands is that clone works to fetch code from a remote repository, alternatively checkout works to switch between versions of code already on the local system. ## Usage: Existing branches Assuming the repo you're working in contains pre-existing branches, you can switch between these branches using `git checkout`. To find out what branches are available and what the current branch name is, execute `git branch`. ``` 1$＞ git branch 2main 3another_branch 4feature_inprogress_branch 5$＞ git checkout feature_inprogress_branch ``` The above example demonstrates how to view a list of available branches by executing the `git branch` command, and switch to a specified branch, in this case, the `feature_inprogress_branch`. ## New branches `Git checkout` works hand-in-hand with [git branch](https://www.atlassian.com/git/tutorials/using-branches). The `git branch` command can be used to create a new branch. When you want to start a new feature, you create a new branch off `main` using `git branch new_branch`. Once created you can then use `git checkout new_branch` to switch to that branch. Additionally, The `git checkout` command accepts a `-b` argument that acts as a convenience method which will create the new branch and immediately switch to it. You can work on multiple features in a single repository by switching between them with `git checkout`. ``` 1git checkout -b ＜new-branch＞ ``` The above example simultaneously creates and checks out `＜new-branch＞`. The `-b` option is a convenience flag that tells Git to run `git branch <new-branch>` before running `git checkout ＜new-branch＞`. ``` 1git checkout -b ＜new-branch＞＜existing-branch＞ ``` By default `git checkout -b` will base the `new-branch` off the current `HEAD`. An optional additional branch parameter can be passed to `git checkout`. In the above example, `＜existing-branch＞` is passed which then bases `new-branch` off of `existing-branch` instead of the current `HEAD`. ## Switching branches Switching branches is a straightforward operation. Executing the following will point `HEAD` to the tip of `＜branchname＞.` ``` 1git checkout ＜branchname＞ ``` Git tracks a history of checkout operations in the reflog. You can execute `git reflog` to view the history. ## Git checkout a remote branch When collaborating with a team it is common to utilize remote repositories. These repositories may be hosted and shared or they may be another colleague's local copy. Each remote repository will contain its own set of branches. In order to checkout a remote branch you have to first fetch the contents of the branch. ``` 1git fetch --all ``` In modern versions of Git, you can then checkout the remote branch like a local branch. ``` 1git checkout ＜remotebranch＞ ``` Older versions of Git require the creation of a new branch based on the `remote`. ``` 1git checkout -b ＜remotebranch＞ origin/＜remotebranch＞ ``` Additionally you can checkout a new local branch and reset it to the remote branches last commit. ``` 1git checkout -b ＜branchname＞ 2git reset --hard origin/＜branchname＞ ``` ## Detached HEADS Now that we’ve seen the three main uses of `git checkout` on branches, it's important to discuss the `“detached HEAD”` state. Remember that the `HEAD` is Git’s way of referring to the current snapshot. Internally, the `git checkout` command simply updates the `HEAD` to point to either the specified branch or commit. When it points to a branch, Git doesn't complain, but when you check out a commit, it switches into a `“detached HEAD”` state. This is a warning telling you that everything you’re doing is “detached” from the rest of your project’s development. If you were to start developing a feature while in a detached `HEAD` state, there would be no branch allowing you to get back to it. When you inevitably check out another branch (e.g., to merge your feature in), there would be no way to reference your feature: ![Attached head vs detached head](https://dam-cdn.atl.orangelogic.com/AssetLink/b01na740f1la476ut2ss5x8pqx7ohq8f.svg) The point is, your development should always take place on a branch—never on a detached `HEAD`. This makes sure you always have a reference to your new commits. However, if you’re just looking at an old commit, it doesn’t really matter if you’re in a detached `HEAD` state or not. ## Summary This page focused on usage of the `git checkout` command when changing branches. In summation, `git checkout`, when used on branches, alters the target of the `HEAD` ref. It can be used to create branches, switch branches, and checkout remote branches. The `git checkout` command is an essential tool for standard Git operation. It is a counterpart to [git merge](https://www.atlassian.com/git/tutorials/using-branches/git-merge). The `git checkout` and `git merge` commands are critical tools to enabling [git workflows](https://www.atlassian.com/git/tutorials/comparing-workflows). ## Recommended for you ### Bitbucket blog [Learn more](https://www.atlassian.com/blog/bitbucket) ### DevOps learning path [Learn more](https://university.atlassian.com/student/activity/2483065-hello-and-welcome) ### Learn more about Git Find more Git guides and resources in this hub. [Read more](https://www.atlassian.com/git) - [Company](https://www.atlassian.com/company) - [Careers](https://www.atlassian.com/company/careers) - [Events](https://www.atlassian.com/company/events) - [Blogs](https://www.atlassian.com/blog) - [Investor Relations](https://investors.atlassian.com/) - [Atlassian Foundation](https://www.atlassianfoundation.org/) - [Press kit](https://www.atlassian.com/company/news/press-kit) - [Contact us](https://www.atlassian.com/company/contact) ## Products - [Rovo](https://www.atlassian.com/rovo) - [Jira](https://www.atlassian.com/software/jira) - [Jira Align](https://www.atlassian.com/software/jira/align) - [Jira Service Management](https://www.atlassian.com/software/jira/service-management) - [Confluence](https://www.atlassian.com/software/confluence) - [Loom](https://www.atlassian.com/software/loom) - [Trello](https://trello.com/home) - [Bitbucket](https://www.atlassian.com/software/bitbucket) - [See all products](https://www.atlassian.com/software) ## Resources - [Technical support](https://support.atlassian.com/) - [Purchasing & licensing](https://www.atlassian.com/licensing/purchase-licensing) - [Atlassian Community](https://community.atlassian.com/) - [Knowledge base](https://confluence.atlassian.com/kb) - [Marketplace](https://marketplace.atlassian.com/) - [My account](https://my.atlassian.com/products/index) - [Create support ticket](https://support.atlassian.com/contact/) ## Learn - [Partners](https://www.atlassian.com/partners) - [Training & certification](https://www.atlassian.com/university) - [Documentation](https://confluence.atlassian.com/display/ALLDOC/Atlassian+Documentation) - [Developer resources](https://www.atlassian.com/developers) - [Enterprise services](https://www.atlassian.com/enterprise/services) - [See all resources](https://www.atlassian.com/resources) Copyright © 2026 Atlassian - [Privacy policy](https://www.atlassian.com/legal/privacy-policy) - [Notice at Collection](https://www.atlassian.com/legal/privacy-policy#additional-disclosures-for-ca-residents) - [Terms](https://www.atlassian.com/legal/cloud-terms-of-service) - [Impressum](https://www.atlassian.com/legal/impressum) Language selector English ▾
Readable Markdown	This page is an examination of the `git checkout` command. It will cover usage examples and edge cases. In Git terms, a "checkout" is the act of switching between different versions of a target entity. The `git checkout` command operates upon three distinct entities: files, commits, and branches. In addition to the definition of "checkout" the phrase "checking out" is commonly used to imply the act of executing the `git checkout` command. In the [Undoing Changes](https://www.atlassian.com/git/tutorials/undoing-changes) topic, we saw how `git checkout` can be used to view old commits. The focus for the majority of this document will be checkout operations on branches. Checking out branches is similar to checking out old commits and files in that the working directory is updated to match the selected branch/revision; however, new changes are saved in the project history—that is, it’s not a read-only operation. Checking out branches The `git checkout` command lets you navigate between the branches created by `git branch`. Checking out a branch updates the files in the working directory to match the version stored in that branch, and it tells Git to record all new commits on that branch. Think of it as a way to select which line of development you’re working on. Having a dedicated branch for each new feature is a dramatic shift from a traditional SVN workflow. It makes it ridiculously easy to try new experiments without the fear of destroying existing functionality, and it makes it possible to work on many unrelated features at the same time. In addition, branches also facilitate several collaborative workflows. The `git checkout` command may occasionally be confused with `git clone`. The difference between the two commands is that clone works to fetch code from a remote repository, alternatively checkout works to switch between versions of code already on the local system. Usage: Existing branches Assuming the repo you're working in contains pre-existing branches, you can switch between these branches using `git checkout`. To find out what branches are available and what the current branch name is, execute `git branch`. ``` $＞ git branch main another_branch feature_inprogress_branch $＞ git checkout feature_inprogress_branch ``` The above example demonstrates how to view a list of available branches by executing the `git branch` command, and switch to a specified branch, in this case, the `feature_inprogress_branch`. New branches `Git checkout` works hand-in-hand with [git branch](https://www.atlassian.com/git/tutorials/using-branches). The `git branch` command can be used to create a new branch. When you want to start a new feature, you create a new branch off `main` using `git branch new_branch`. Once created you can then use `git checkout new_branch` to switch to that branch. Additionally, The `git checkout` command accepts a `-b` argument that acts as a convenience method which will create the new branch and immediately switch to it. You can work on multiple features in a single repository by switching between them with `git checkout`. ``` git checkout -b ＜new-branch＞ ``` The above example simultaneously creates and checks out `＜new-branch＞`. The `-b` option is a convenience flag that tells Git to run `git branch <new-branch>` before running `git checkout ＜new-branch＞`. ``` git checkout -b ＜new-branch＞＜existing-branch＞ ``` By default `git checkout -b` will base the `new-branch` off the current `HEAD`. An optional additional branch parameter can be passed to `git checkout`. In the above example, `＜existing-branch＞` is passed which then bases `new-branch` off of `existing-branch` instead of the current `HEAD`. Switching branches Switching branches is a straightforward operation. Executing the following will point `HEAD` to the tip of `＜branchname＞.` ``` git checkout ＜branchname＞ ``` Git tracks a history of checkout operations in the reflog. You can execute `git reflog` to view the history. Git checkout a remote branch When collaborating with a team it is common to utilize remote repositories. These repositories may be hosted and shared or they may be another colleague's local copy. Each remote repository will contain its own set of branches. In order to checkout a remote branch you have to first fetch the contents of the branch. ``` git fetch --all ``` In modern versions of Git, you can then checkout the remote branch like a local branch. ``` git checkout ＜remotebranch＞ ``` Older versions of Git require the creation of a new branch based on the `remote`. ``` git checkout -b ＜remotebranch＞ origin/＜remotebranch＞ ``` Additionally you can checkout a new local branch and reset it to the remote branches last commit. ``` git checkout -b ＜branchname＞ git reset --hard origin/＜branchname＞ ``` Detached HEADS Now that we’ve seen the three main uses of `git checkout` on branches, it's important to discuss the `“detached HEAD”` state. Remember that the `HEAD` is Git’s way of referring to the current snapshot. Internally, the `git checkout` command simply updates the `HEAD` to point to either the specified branch or commit. When it points to a branch, Git doesn't complain, but when you check out a commit, it switches into a `“detached HEAD”` state. This is a warning telling you that everything you’re doing is “detached” from the rest of your project’s development. If you were to start developing a feature while in a detached `HEAD` state, there would be no branch allowing you to get back to it. When you inevitably check out another branch (e.g., to merge your feature in), there would be no way to reference your feature: ![Attached head vs detached head](https://dam-cdn.atl.orangelogic.com/AssetLink/b01na740f1la476ut2ss5x8pqx7ohq8f.svg) The point is, your development should always take place on a branch—never on a detached `HEAD`. This makes sure you always have a reference to your new commits. However, if you’re just looking at an old commit, it doesn’t really matter if you’re in a detached `HEAD` state or not. Summary This page focused on usage of the `git checkout` command when changing branches. In summation, `git checkout`, when used on branches, alters the target of the `HEAD` ref. It can be used to create branches, switch branches, and checkout remote branches. The `git checkout` command is an essential tool for standard Git operation. It is a counterpart to [git merge](https://www.atlassian.com/git/tutorials/using-branches/git-merge). The `git checkout` and `git merge` commands are critical tools to enabling [git workflows](https://www.atlassian.com/git/tutorials/comparing-workflows).
Shard	44 (laksa)
Root Hash	11161217235333269644
Unparsed URL	com,atlassian!www,/git/tutorials/using-branches/git-checkout s443