🕷️ Crawler Inspector

URL Lookup

Direct Parameter Lookup

Raw Queries and Responses

1. Shard Calculation

Query:

Response:

Calculated Shard: 1 (from laksa010)

2. Crawled Status Check

Query:

curl -X POST \
  'http://laksa001.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://betterstack.com/community/questions/move-uncommited-work-to-new-branch/\')), getAhrefsUnparsedNoserviceFromURL(\'https://betterstack.com/community/questions/move-uncommited-work-to-new-branch/\'))) FORMAT JSONEachRow'

Response:

{"found_url":"https:\/\/betterstack.com\/community\/questions\/move-uncommited-work-to-new-branch\/","crawl_time":1775021853,"first_indexed_time":1719518532,"http_code":200,"src_unparsed":"com,betterstack!\/community\/questions\/move-uncommited-work-to-new-branch\/ s443","src_root_hash":"1143718778839325401","history_drop_reason":null,"meta_title":"Move Existing, Uncommitted Work to a New Branch in Git | Better Stack Community","meta_descriptions":["AI SRE and MCP server, incident management, on-call, logs, metrics, traces, and error tracking. 7,000+ happy customers. 60-day money back guarantee."],"attrs_boilerpipe_text":"Better Stack Team\nUpdated on June 24, 2024\nTo move existing, uncommitted work to a new branch in Git, you can follow these steps:\nStep 1: Check Uncommitted Changes\nFirst, make sure you have uncommitted changes in your working directory. You can check the status of your working directory using:\nCopied!\nStep 2: Create a New Branch\nCreate a new branch to move your uncommitted changes to. You can use the following command to create a new branch:\nCopied!\nReplace\n<new-branch-name>\nwith the name of your new branch.\nStep 3: Commit Changes to the New Branch\nCommit your changes to the new branch using:\nCopied!\nStep 4: Switch Back to the Original Branch (Optional)\nIf you want to switch back to the original branch, you can do so using:\nCopied!\nNote:\nBe careful when creating a new branch and committing changes. Ensure that the changes you're committing belong to the new branch and are not intended for the original branch.\nIf you have staged changes that you don't want to commit to the new branch, you can unstage them using\ngit reset HEAD <file>\nbefore committing.\nIf you haven't staged all your changes and want to include them in the new branch, you can use\ngit stash\nto temporarily store them and then apply them in the new branch after switching.\nGot an article suggestion?\nLet us know\nExplore more\nThis work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.","attrs_markdown":"Platform\n\n[AI SRE Agentic root cause analysis](https:\/\/betterstack.com\/ai-sre)\n\n[Incident management & on-call Move fast when things break](https:\/\/betterstack.com\/incident-management)\n\n[Uptime monitoring The most reliable uptime monitoring](https:\/\/betterstack.com\/uptime)\n\n[Status page Communicate downtime & build trust](https:\/\/betterstack.com\/status-page)\n\n[Tracing eBPF-based OpenTelemetry-native tracing](https:\/\/betterstack.com\/tracing)\n\n[Log management Collect insights across your stack](https:\/\/betterstack.com\/log-management)\n\n[Infrastructure monitoring OpenTelemetry-native infrastructure monitoring](https:\/\/betterstack.com\/infrastructure-monitoring)\n\n[Real user monitoring Session replay, web vitals & product analytics](https:\/\/betterstack.com\/real-user-monitoring)\n\n[Error tracking AI‑native error tracking built on Better Stack](https:\/\/betterstack.com\/error-tracking)\n\n[Data warehouse Time series data warehouse as an API](https:\/\/betterstack.com\/warehouse)\n\n[Documentation](https:\/\/betterstack.com\/docs\/)   [Pricing](https:\/\/betterstack.com\/pricing)\n\nCompany\n\n[Work at Better Stack](https:\/\/betterstack.com\/careers)\n\n[Engineering](https:\/\/betterstack.com\/careers\/engineering)\n\n[Security](https:\/\/betterstack.com\/security)\n\n[Blog](https:\/\/betterstack.com\/community\/blog)\n\n[Changelog](https:\/\/betterstack.com\/tag\/changelog)\n\n[Enterprise](https:\/\/betterstack.com\/enterprise)\n\n[Sign in](https:\/\/betterstack.com\/users\/sign-in) [Sign up](https:\/\/betterstack.com\/users\/sign-up)\n\nPlatform\n\n[Documentation](https:\/\/betterstack.com\/docs\/) [Pricing](https:\/\/betterstack.com\/pricing)\n\nCommunity\n\nCompany\n\n[Enterprise](https:\/\/betterstack.com\/enterprise)\n\nBack\n\n[AI SRE Agentic root cause analysis](https:\/\/betterstack.com\/ai-sre)\n\n[Incident management & on-call Move fast when things break](https:\/\/betterstack.com\/incident-management)\n\n[Uptime monitoring The most reliable uptime monitoring](https:\/\/betterstack.com\/uptime)\n\n[Status page Communicate downtime & build trust](https:\/\/betterstack.com\/status-page)\n\n[Tracing eBPF-based OpenTelemetry-native tracing](https:\/\/betterstack.com\/tracing)\n\n[Log management Collect insights across your stack](https:\/\/betterstack.com\/log-management)\n\n[Infrastructure monitoring OpenTelemetry-native infrastructure monitoring](https:\/\/betterstack.com\/infrastructure-monitoring)\n\n[Real user monitoring Session replay, web vitals & product analytics](https:\/\/betterstack.com\/real-user-monitoring)\n\n[Error tracking AI‑native error tracking built on Better Stack](https:\/\/betterstack.com\/error-tracking)\n\n[Data warehouse Time series data warehouse as an API](https:\/\/betterstack.com\/warehouse)\n\nBack\n\n[Community home](https:\/\/betterstack.com\/community)\n\n[Guides](https:\/\/betterstack.com\/community\/guides)\n\n[Questions](https:\/\/betterstack.com\/community\/questions)\n\n[Comparisons](https:\/\/betterstack.com\/community\/comparisons)\n\nBack\n\n[Work at Better Stack](https:\/\/betterstack.com\/careers)\n\n[Engineering](https:\/\/betterstack.com\/careers\/engineering)\n\n[Security](https:\/\/betterstack.com\/security)\n\n[Blog](https:\/\/betterstack.com\/community\/blog)\n\n[Changelog](https:\/\/betterstack.com\/tag\/changelog)\n\nQuestions\n\n[Community](https:\/\/betterstack.com\/community\/?utm_content&utm_medium=questions&utm_source=community&utm_term=move-uncommited-work-to-new-branch)   [Guides](https:\/\/betterstack.com\/community\/guides\/?utm_content&utm_medium=questions&utm_source=community&utm_term=move-uncommited-work-to-new-branch)   [Questions](https:\/\/betterstack.com\/community\/questions\/?utm_content&utm_medium=questions&utm_source=community&utm_term=move-uncommited-work-to-new-branch)   [Comparisons](https:\/\/betterstack.com\/community\/comparisons\/?utm_content&utm_medium=questions&utm_source=community&utm_term=move-uncommited-work-to-new-branch)   [Blog](https:\/\/betterstack.com\/community\/blog\/?utm_content&utm_medium=questions&utm_source=community&utm_term=move-uncommited-work-to-new-branch)\n\n- [Community](https:\/\/betterstack.com\/community\/?utm_content&utm_medium=questions&utm_source=community&utm_term=move-uncommited-work-to-new-branch)\n- [Guides](https:\/\/betterstack.com\/community\/guides\/?utm_content&utm_medium=questions&utm_source=community&utm_term=move-uncommited-work-to-new-branch)\n- [Questions](https:\/\/betterstack.com\/community\/questions\/?utm_content&utm_medium=questions&utm_source=community&utm_term=move-uncommited-work-to-new-branch)\n- [Comparisons](https:\/\/betterstack.com\/community\/comparisons\/?utm_content&utm_medium=questions&utm_source=community&utm_term=move-uncommited-work-to-new-branch)\n- [Blog](https:\/\/betterstack.com\/community\/blog\/?utm_content&utm_medium=questions&utm_source=community&utm_term=move-uncommited-work-to-new-branch)\n\n[Docs](https:\/\/betterstack.com\/docs\/) [Documentation](https:\/\/betterstack.com\/docs\/)\n\n# Move Existing, Uncommitted Work to a New Branch in Git\nBetter Stack Team\n\nUpdated on June 24, 2024\n\nTo move existing, uncommitted work to a new branch in Git, you can follow these steps:\n\n### Step 1: Check Uncommitted Changes\nFirst, make sure you have uncommitted changes in your working directory. You can check the status of your working directory using:\n\nCopied\\!\n```\ngit status\n```\n### Step 2: Create a New Branch\nCreate a new branch to move your uncommitted changes to. You can use the following command to create a new branch:\n\nCopied\\!\n```\ngit checkout -b <new-branch-name>\n```\n\nReplace `<new-branch-name>` with the name of your new branch.\n\n### Step 3: Commit Changes to the New Branch\nCommit your changes to the new branch using:\n\nCopied\\!\n```\ngit add .\ngit commit -m \"Your commit message\"\n```\n### Step 4: Switch Back to the Original Branch (Optional)\nIf you want to switch back to the original branch, you can do so using:\n\nCopied\\!\n```\ngit checkout <original-branch-name>\n```\n### Note:\n- Be careful when creating a new branch and committing changes. Ensure that the changes you're committing belong to the new branch and are not intended for the original branch.\n- If you have staged changes that you don't want to commit to the new branch, you can unstage them using `git reset HEAD <file>` before committing.\n- If you haven't staged all your changes and want to include them in the new branch, you can use `git stash` to temporarily store them and then apply them in the new branch after switching.\n\nGot an article suggestion? [Let us know](mailto:hello@betterstack.com?subject=Suggestion%20for%20Move%20Existing%2C%20Uncommitted%20Work%20to%20a%20New%20Branch%20in%20Git&body=)\n\nExplore more\n\n[Git](https:\/\/betterstack.com\/tag\/git)\n\n[What Is the Difference between ‘Git Pull’ and ‘Git Fetch’? git pull and git fetch are both Git commands used to update your local repository with changes from a remote repository. However, they work differently. ![]() Questions](https:\/\/betterstack.com\/community\/questions\/git-pull-vs-git-fetch\/)\n\n[How to Determine the URL That a Local Git Repository Was Originally Cloned From ![]() Questions](https:\/\/betterstack.com\/community\/questions\/how-to-determine-url-that-local-git-repo-was-originally-cloned-from\/)\n\n[![Licensed under CC-BY-NC-SA]()](https:\/\/creativecommons.org\/licenses\/by-nc-sa\/4.0\/)\n\nThis work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.\n\n- [What Is the Difference between ‘Git Pull’ and ‘Git Fetch’? git pull and git fetch are both Git commands used to update your local repository with changes from a remote repository. However, they work differently. ![]() Questions](https:\/\/betterstack.com\/community\/questions\/git-pull-vs-git-fetch\/)\n- [How to Determine the URL That a Local Git Repository Was Originally Cloned From To determine the URL that a local Git repository was originally cloned from, you can use the git remote command with the -v option. Here's how: git remote -v This command will display the URLs asso... ![]() Questions](https:\/\/betterstack.com\/community\/questions\/how-to-determine-url-that-local-git-repo-was-originally-cloned-from\/)\n\nSolutions\n\n[AI SRE](https:\/\/betterstack.com\/ai-sre)   \n [OpenTelemetry tracing](https:\/\/betterstack.com\/tracing)   \n [Log management](https:\/\/betterstack.com\/telemetry)   \n [Infrastructure monitoring](https:\/\/betterstack.com\/infrastructure-monitoring)   \n [Error tracking](https:\/\/betterstack.com\/error-tracking)   \n [Real user monitoring](https:\/\/betterstack.com\/real-user-monitoring)   \n [Incident management](https:\/\/betterstack.com\/incident-management)   \n [Uptime monitoring](https:\/\/betterstack.com\/uptime)   \n [Status page](https:\/\/betterstack.com\/status-page)   \n [Data warehouse](https:\/\/betterstack.com\/warehouse)\n\nCompany\n\n[Work at Better Stack](https:\/\/betterstack.com\/careers)   \n [Engineering](https:\/\/betterstack.com\/careers\/engineering)   \n [Security](https:\/\/betterstack.com\/security)\n\nResources\n\n[Help & Support](https:\/\/betterstack.com\/help)   \n [Documentation](https:\/\/betterstack.com\/docs\/)   \n [Enterprise](https:\/\/betterstack.com\/enterprise)   \n [Integrations](https:\/\/betterstack.com\/integrations)   \n [Dashboards](https:\/\/betterstack.com\/dashboards)\n\nCompany\n\n[Work at Better Stack](https:\/\/betterstack.com\/careers)   \n [Engineering](https:\/\/betterstack.com\/careers\/engineering)   \n [Security](https:\/\/betterstack.com\/security)\n\nResources\n\n[Help & Support](https:\/\/betterstack.com\/help)   \n [Documentation](https:\/\/betterstack.com\/docs\/)   \n [Enterprise](https:\/\/betterstack.com\/enterprise)   \n [Integrations](https:\/\/betterstack.com\/integrations)   \n [Dashboards](https:\/\/betterstack.com\/dashboards)\n\nCommunity\n\n[What Is Incident Management? Beginner’s Guide](https:\/\/betterstack.com\/community\/guides\/incident-management\/what-is-incident-management\/) [Best Datadog Alternatives to Consider in 2026](https:\/\/betterstack.com\/community\/comparisons\/datadog-log-management-alternatives\/) [8 Best Free & Open Source Status Page Tools in 2026](https:\/\/betterstack.com\/community\/comparisons\/free-status-page-tools\/) [13 Best Sentry Alternatives in 2026](https:\/\/betterstack.com\/community\/comparisons\/sentry-alternatives\/) [15 Best Grafana Alternatives in 2026](https:\/\/betterstack.com\/community\/comparisons\/grafana-alternatives\/) [The 10 Best Incident.io Alternatives in 2026](https:\/\/betterstack.com\/community\/comparisons\/incident-io-alternative\/) [5 Most Used Incident Management Tools](https:\/\/betterstack.com\/community\/comparisons\/incident-management-tools\/)\n\n30x cheaper than Datadog. Predictable pricing. Exceptional customer support.\n\n[\\+1 (628) 900-3830](<tel:+1 (628) 900-3830>) [hello@betterstack.com](mailto:hello@betterstack.com)\n\n[Terms of Use](https:\/\/betterstack.com\/terms) [Privacy Policy](https:\/\/betterstack.com\/privacy) [GDPR](https:\/\/betterstack.com\/dpa)\n\n[System status](https:\/\/status.betterstack.com\/)\n\n© 2026 Better Stack, Inc.\n\n### Please accept cookies\nWe use cookies to authenticate users, improve the product user experience, and for [personalized ads](https:\/\/business.safety.google\/privacy\/). [Learn more.](https:\/\/betterstack.com\/privacy)\n\nDeny\n\nAccept required\n\nAccept all","attrs_readable_markdown":"Better Stack Team\n\nUpdated on June 24, 2024\n\nTo move existing, uncommitted work to a new branch in Git, you can follow these steps:\n\n### Step 1: Check Uncommitted Changes\nFirst, make sure you have uncommitted changes in your working directory. You can check the status of your working directory using:\n\nCopied\\!\n\n### Step 2: Create a New Branch\nCreate a new branch to move your uncommitted changes to. You can use the following command to create a new branch:\n\nCopied\\!\n\nReplace `<new-branch-name>` with the name of your new branch.\n\n### Step 3: Commit Changes to the New Branch\nCommit your changes to the new branch using:\n\nCopied\\!\n\n### Step 4: Switch Back to the Original Branch (Optional)\nIf you want to switch back to the original branch, you can do so using:\n\nCopied\\!\n\n### Note:\n- Be careful when creating a new branch and committing changes. Ensure that the changes you're committing belong to the new branch and are not intended for the original branch.\n- If you have staged changes that you don't want to commit to the new branch, you can unstage them using `git reset HEAD <file>` before committing.\n- If you haven't staged all your changes and want to include them in the new branch, you can use `git stash` to temporarily store them and then apply them in the new branch after switching.\n\nGot an article suggestion? [Let us know](mailto:hello@betterstack.com?subject=Suggestion%20for%20Move%20Existing%2C%20Uncommitted%20Work%20to%20a%20New%20Branch%20in%20Git&body=)\n\nExplore more\n\n[![Licensed under CC-BY-NC-SA](https:\/\/betterstack.com\/assets\/articles\/cc-by-nc-sa-198c1f75.png)](https:\/\/creativecommons.org\/licenses\/by-nc-sa\/4.0\/)\n\nThis work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.","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://betterstack.com/community/questions/move-uncommited-work-to-new-branch/
Last Crawled	2026-04-01 05:37:33 (8 days ago)
First Indexed	2024-06-27 20:02:12 (1 year ago)
HTTP Status Code	200
Meta Title	Move Existing, Uncommitted Work to a New Branch in Git \| Better Stack Community
Meta Description	AI SRE and MCP server, incident management, on-call, logs, metrics, traces, and error tracking. 7,000+ happy customers. 60-day money back guarantee.
Meta Canonical	null
Boilerpipe Text	Better Stack Team Updated on June 24, 2024 To move existing, uncommitted work to a new branch in Git, you can follow these steps: Step 1: Check Uncommitted Changes First, make sure you have uncommitted changes in your working directory. You can check the status of your working directory using: Copied! Step 2: Create a New Branch Create a new branch to move your uncommitted changes to. You can use the following command to create a new branch: Copied! Replace <new-branch-name> with the name of your new branch. Step 3: Commit Changes to the New Branch Commit your changes to the new branch using: Copied! Step 4: Switch Back to the Original Branch (Optional) If you want to switch back to the original branch, you can do so using: Copied! Note: Be careful when creating a new branch and committing changes. Ensure that the changes you're committing belong to the new branch and are not intended for the original branch. If you have staged changes that you don't want to commit to the new branch, you can unstage them using git reset HEAD <file> before committing. If you haven't staged all your changes and want to include them in the new branch, you can use git stash to temporarily store them and then apply them in the new branch after switching. Got an article suggestion? Let us know Explore more This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Markdown	Platform [AI SRE Agentic root cause analysis](https://betterstack.com/ai-sre) [Incident management & on-call Move fast when things break](https://betterstack.com/incident-management) [Uptime monitoring The most reliable uptime monitoring](https://betterstack.com/uptime) [Status page Communicate downtime & build trust](https://betterstack.com/status-page) [Tracing eBPF-based OpenTelemetry-native tracing](https://betterstack.com/tracing) [Log management Collect insights across your stack](https://betterstack.com/log-management) [Infrastructure monitoring OpenTelemetry-native infrastructure monitoring](https://betterstack.com/infrastructure-monitoring) [Real user monitoring Session replay, web vitals & product analytics](https://betterstack.com/real-user-monitoring) [Error tracking AI‑native error tracking built on Better Stack](https://betterstack.com/error-tracking) [Data warehouse Time series data warehouse as an API](https://betterstack.com/warehouse) [Documentation](https://betterstack.com/docs/) [Pricing](https://betterstack.com/pricing) Company [Work at Better Stack](https://betterstack.com/careers) [Engineering](https://betterstack.com/careers/engineering) [Security](https://betterstack.com/security) [Blog](https://betterstack.com/community/blog) [Changelog](https://betterstack.com/tag/changelog) [Enterprise](https://betterstack.com/enterprise) [Sign in](https://betterstack.com/users/sign-in) [Sign up](https://betterstack.com/users/sign-up) Platform [Documentation](https://betterstack.com/docs/) [Pricing](https://betterstack.com/pricing) Community Company [Enterprise](https://betterstack.com/enterprise) Back [AI SRE Agentic root cause analysis](https://betterstack.com/ai-sre) [Incident management & on-call Move fast when things break](https://betterstack.com/incident-management) [Uptime monitoring The most reliable uptime monitoring](https://betterstack.com/uptime) [Status page Communicate downtime & build trust](https://betterstack.com/status-page) [Tracing eBPF-based OpenTelemetry-native tracing](https://betterstack.com/tracing) [Log management Collect insights across your stack](https://betterstack.com/log-management) [Infrastructure monitoring OpenTelemetry-native infrastructure monitoring](https://betterstack.com/infrastructure-monitoring) [Real user monitoring Session replay, web vitals & product analytics](https://betterstack.com/real-user-monitoring) [Error tracking AI‑native error tracking built on Better Stack](https://betterstack.com/error-tracking) [Data warehouse Time series data warehouse as an API](https://betterstack.com/warehouse) Back [Community home](https://betterstack.com/community) [Guides](https://betterstack.com/community/guides) [Questions](https://betterstack.com/community/questions) [Comparisons](https://betterstack.com/community/comparisons) Back [Work at Better Stack](https://betterstack.com/careers) [Engineering](https://betterstack.com/careers/engineering) [Security](https://betterstack.com/security) [Blog](https://betterstack.com/community/blog) [Changelog](https://betterstack.com/tag/changelog) Questions [Community](https://betterstack.com/community/?utm_content&utm_medium=questions&utm_source=community&utm_term=move-uncommited-work-to-new-branch) [Guides](https://betterstack.com/community/guides/?utm_content&utm_medium=questions&utm_source=community&utm_term=move-uncommited-work-to-new-branch) [Questions](https://betterstack.com/community/questions/?utm_content&utm_medium=questions&utm_source=community&utm_term=move-uncommited-work-to-new-branch) [Comparisons](https://betterstack.com/community/comparisons/?utm_content&utm_medium=questions&utm_source=community&utm_term=move-uncommited-work-to-new-branch) [Blog](https://betterstack.com/community/blog/?utm_content&utm_medium=questions&utm_source=community&utm_term=move-uncommited-work-to-new-branch) - [Community](https://betterstack.com/community/?utm_content&utm_medium=questions&utm_source=community&utm_term=move-uncommited-work-to-new-branch) - [Guides](https://betterstack.com/community/guides/?utm_content&utm_medium=questions&utm_source=community&utm_term=move-uncommited-work-to-new-branch) - [Questions](https://betterstack.com/community/questions/?utm_content&utm_medium=questions&utm_source=community&utm_term=move-uncommited-work-to-new-branch) - [Comparisons](https://betterstack.com/community/comparisons/?utm_content&utm_medium=questions&utm_source=community&utm_term=move-uncommited-work-to-new-branch) - [Blog](https://betterstack.com/community/blog/?utm_content&utm_medium=questions&utm_source=community&utm_term=move-uncommited-work-to-new-branch) [Docs](https://betterstack.com/docs/) [Documentation](https://betterstack.com/docs/) # Move Existing, Uncommitted Work to a New Branch in Git Better Stack Team Updated on June 24, 2024 To move existing, uncommitted work to a new branch in Git, you can follow these steps: ### Step 1: Check Uncommitted Changes First, make sure you have uncommitted changes in your working directory. You can check the status of your working directory using: Copied\! ``` git status ``` ### Step 2: Create a New Branch Create a new branch to move your uncommitted changes to. You can use the following command to create a new branch: Copied\! ``` git checkout -b <new-branch-name> ``` Replace `<new-branch-name>` with the name of your new branch. ### Step 3: Commit Changes to the New Branch Commit your changes to the new branch using: Copied\! ``` git add . git commit -m "Your commit message" ``` ### Step 4: Switch Back to the Original Branch (Optional) If you want to switch back to the original branch, you can do so using: Copied\! ``` git checkout <original-branch-name> ``` ### Note: - Be careful when creating a new branch and committing changes. Ensure that the changes you're committing belong to the new branch and are not intended for the original branch. - If you have staged changes that you don't want to commit to the new branch, you can unstage them using `git reset HEAD <file>` before committing. - If you haven't staged all your changes and want to include them in the new branch, you can use `git stash` to temporarily store them and then apply them in the new branch after switching. Got an article suggestion? [Let us know](mailto:hello@betterstack.com?subject=Suggestion%20for%20Move%20Existing%2C%20Uncommitted%20Work%20to%20a%20New%20Branch%20in%20Git&body=) Explore more [Git](https://betterstack.com/tag/git) [What Is the Difference between ‘Git Pull’ and ‘Git Fetch’? git pull and git fetch are both Git commands used to update your local repository with changes from a remote repository. However, they work differently. ![]() Questions](https://betterstack.com/community/questions/git-pull-vs-git-fetch/) [How to Determine the URL That a Local Git Repository Was Originally Cloned From ![]() Questions](https://betterstack.com/community/questions/how-to-determine-url-that-local-git-repo-was-originally-cloned-from/) [![Licensed under CC-BY-NC-SA]()](https://creativecommons.org/licenses/by-nc-sa/4.0/) This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License. - [What Is the Difference between ‘Git Pull’ and ‘Git Fetch’? git pull and git fetch are both Git commands used to update your local repository with changes from a remote repository. However, they work differently. ![]() Questions](https://betterstack.com/community/questions/git-pull-vs-git-fetch/) - [How to Determine the URL That a Local Git Repository Was Originally Cloned From To determine the URL that a local Git repository was originally cloned from, you can use the git remote command with the -v option. Here's how: git remote -v This command will display the URLs asso... ![]() Questions](https://betterstack.com/community/questions/how-to-determine-url-that-local-git-repo-was-originally-cloned-from/) Solutions [AI SRE](https://betterstack.com/ai-sre) [OpenTelemetry tracing](https://betterstack.com/tracing) [Log management](https://betterstack.com/telemetry) [Infrastructure monitoring](https://betterstack.com/infrastructure-monitoring) [Error tracking](https://betterstack.com/error-tracking) [Real user monitoring](https://betterstack.com/real-user-monitoring) [Incident management](https://betterstack.com/incident-management) [Uptime monitoring](https://betterstack.com/uptime) [Status page](https://betterstack.com/status-page) [Data warehouse](https://betterstack.com/warehouse) Company [Work at Better Stack](https://betterstack.com/careers) [Engineering](https://betterstack.com/careers/engineering) [Security](https://betterstack.com/security) Resources [Help & Support](https://betterstack.com/help) [Documentation](https://betterstack.com/docs/) [Enterprise](https://betterstack.com/enterprise) [Integrations](https://betterstack.com/integrations) [Dashboards](https://betterstack.com/dashboards) Company [Work at Better Stack](https://betterstack.com/careers) [Engineering](https://betterstack.com/careers/engineering) [Security](https://betterstack.com/security) Resources [Help & Support](https://betterstack.com/help) [Documentation](https://betterstack.com/docs/) [Enterprise](https://betterstack.com/enterprise) [Integrations](https://betterstack.com/integrations) [Dashboards](https://betterstack.com/dashboards) Community [What Is Incident Management? Beginner’s Guide](https://betterstack.com/community/guides/incident-management/what-is-incident-management/) [Best Datadog Alternatives to Consider in 2026](https://betterstack.com/community/comparisons/datadog-log-management-alternatives/) [8 Best Free & Open Source Status Page Tools in 2026](https://betterstack.com/community/comparisons/free-status-page-tools/) [13 Best Sentry Alternatives in 2026](https://betterstack.com/community/comparisons/sentry-alternatives/) [15 Best Grafana Alternatives in 2026](https://betterstack.com/community/comparisons/grafana-alternatives/) [The 10 Best Incident.io Alternatives in 2026](https://betterstack.com/community/comparisons/incident-io-alternative/) [5 Most Used Incident Management Tools](https://betterstack.com/community/comparisons/incident-management-tools/) 30x cheaper than Datadog. Predictable pricing. Exceptional customer support. [\+1 (628) 900-3830](<tel:+1 (628) 900-3830>) [hello@betterstack.com](mailto:hello@betterstack.com) [Terms of Use](https://betterstack.com/terms) [Privacy Policy](https://betterstack.com/privacy) [GDPR](https://betterstack.com/dpa) [System status](https://status.betterstack.com/) © 2026 Better Stack, Inc. ### Please accept cookies We use cookies to authenticate users, improve the product user experience, and for [personalized ads](https://business.safety.google/privacy/). [Learn more.](https://betterstack.com/privacy) Deny Accept required Accept all
Readable Markdown	Better Stack Team Updated on June 24, 2024 To move existing, uncommitted work to a new branch in Git, you can follow these steps: ### Step 1: Check Uncommitted Changes First, make sure you have uncommitted changes in your working directory. You can check the status of your working directory using: Copied\! ### Step 2: Create a New Branch Create a new branch to move your uncommitted changes to. You can use the following command to create a new branch: Copied\! Replace `<new-branch-name>` with the name of your new branch. ### Step 3: Commit Changes to the New Branch Commit your changes to the new branch using: Copied\! ### Step 4: Switch Back to the Original Branch (Optional) If you want to switch back to the original branch, you can do so using: Copied\! ### Note: - Be careful when creating a new branch and committing changes. Ensure that the changes you're committing belong to the new branch and are not intended for the original branch. - If you have staged changes that you don't want to commit to the new branch, you can unstage them using `git reset HEAD <file>` before committing. - If you haven't staged all your changes and want to include them in the new branch, you can use `git stash` to temporarily store them and then apply them in the new branch after switching. Got an article suggestion? [Let us know](mailto:hello@betterstack.com?subject=Suggestion%20for%20Move%20Existing%2C%20Uncommitted%20Work%20to%20a%20New%20Branch%20in%20Git&body=) Explore more [![Licensed under CC-BY-NC-SA](https://betterstack.com/assets/articles/cc-by-nc-sa-198c1f75.png)](https://creativecommons.org/licenses/by-nc-sa/4.0/) This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.
Shard	1 (laksa)
Root Hash	1143718778839325401
Unparsed URL	com,betterstack!/community/questions/move-uncommited-work-to-new-branch/ s443