🕷️ Crawler Inspector

URL Lookup

Direct Parameter Lookup

Raw Queries and Responses

1. Shard Calculation

Query:

Response:

Calculated Shard: 67 (from laksa142)

2. Crawled Status Check

Query:

curl -X POST \
  'http://laksa067.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, ml_categories_json AS ml_categories_json, ml_types_json AS ml_types_json, ml_intent_types_json AS ml_intent_types_json, meta_language AS meta_language, attrs_author AS attrs_author, ifNull(toUnixTimestamp(attrs_publish_time), 0) AS attrs_publish_time, ifNull(toUnixTimestamp(attrs_original_publish_time), 0) AS attrs_original_publish_time, ifNull(attrs_is_republished, 0) AS attrs_is_republished, ifNull(attrs_nr_words, 0) AS attrs_nr_words, ifNull(attrs_boilerpipe_nr_words, 0) AS attrs_boilerpipe_nr_words, ifNull(body_ext_links_number, 0) AS body_ext_links_number, ifNull(body_int_links_number, 0) AS body_int_links_number, ifNull(meta_nofollow, 0) AS meta_nofollow, ifNull(meta_noarchive, 0) AS meta_noarchive, ifNull(props_was_rendered, 0) AS props_was_rendered, ifNull(src_redirect, \'\') AS src_redirect, ifNull(download_time_msec, 0) AS download_time_msec, ifNull(download_ttfb_msec, 0) AS download_ttfb_msec, ifNull(download_size, 0) AS download_size FROM crawler3.page_info_local FINAL PREWHERE (src_root_hash, src_unparsed) IN ((getAhrefsRootHashFromUnparsed(getAhrefsUnparsedNoserviceFromURL(\'https://www.endpointdev.com/blog/2012/06/moving-commit-to-another-branch-in-git/\')), getAhrefsUnparsedNoserviceFromURL(\'https://www.endpointdev.com/blog/2012/06/moving-commit-to-another-branch-in-git/\'))) FORMAT JSONEachRow'

Response:

{"found_url":"https:\/\/www.endpointdev.com\/blog\/2012\/06\/moving-commit-to-another-branch-in-git\/","crawl_time":1776287029,"first_indexed_time":1634941103,"http_code":200,"src_unparsed":"com,endpointdev!www,\/blog\/2012\/06\/moving-commit-to-another-branch-in-git\/ s443","src_root_hash":"15777514137560783467","history_drop_reason":null,"meta_title":"Moving a Commit to Another Branch in Git | End Point Dev","meta_descriptions":[],"attrs_boilerpipe_text":"Perhaps you’ve made the same mistake I have. You’re right in the middle of developing a feature when a request comes up to fix a different completely unrelated problem. So, you jump right in and fix the issue and then you realize you forgot to start a new git feature branch. Suddenly you realize that you need to merge just the fix you made, but don’t want to merge the commits from the previous feature your working on.\nGit rocks at manipulating branches and I knew this, but I wasn’t sure how to just move one commit to the master branch. After some digging and a little trial and error, I finally figured it out. This may not be the simplest approach, but it worked for me and wanted to share.\nThe branches I’ll be working with are master and feature. In the current scenario, the feature branch is 4 commits ahead of the master and the branch that I want to bring over is just the most recent.\nFirst things first, I need to ensure my master branch is up to date.\ngit checkout master\ngit pull origin master\nThen I’ll checkout my feature branch and make sure it’s completely up to date with the master branch.\ngit checkout feature\ngit rebase origin\/master\nNext, I’ll create a temporary feature branch that I’ll use later on to bring over the commit that I want.\ngit checkout -b feature_tmp\nI’ll do the same for master so that I can perform my merging and rebasing in isolation from the master branch.\ngit checkout master\ngit checkout -b master_tmp\nNow I’m going to merge the two tmp branches so that I have a history that contains all of my commits. This will give me the history that I want, but will include the 3 commits I don’t want.\ngit merge feature_tmp\nHere’s where the magic happens. I’m going to rebase this branch using interactive mode. I want to rebase everything back to the last commit on the master branch. For simplicity in the commands here, we’ll just use SHA-MASTER in place of the actual SHA1 hash.\ngit rebase -i SHA-MASTER\nThis loads the commits into my editor and from here I just delete the 3 commits that I didn’t want on my master branch. This will give me the history I want with the 4th commit coming right after the last commit on the master branch. After deleting the commits, I just save and quit my editor.\nNext, I merge my tmp branch into the master branch.\ngit checkout master\ngit merge master_tmp\ngit log\nNow in the log, I can see the history is in the correct order, just how I wanted it. To finish things up, I’ll just push my changes and then rebase my feature branch which will reorder my commits to match the master branch and place my feature commits as the last three commits in the log.\ngit push origin master\ngit checkout feature\ngit rebase origin\/master\ngit log\nThe last thing to do is delete my tmp branches.\ngit branch -D tmp_master\ngit branch -D tmp_feature\ngit","attrs_markdown":"[Skip to content](https:\/\/www.endpointdev.com\/blog\/2012\/06\/moving-commit-to-another-branch-in-git\/#main-content)\n\n×\n\n[Home](https:\/\/www.endpointdev.com\/)\n***\n[Custom Ecommerce](https:\/\/www.endpointdev.com\/custom-ecommerce\/)\n\n[Application Development](https:\/\/www.endpointdev.com\/application-development\/)\n\n[Database Consulting](https:\/\/www.endpointdev.com\/database-consulting\/)\n\n[Cloud Hosting](https:\/\/www.endpointdev.com\/cloud-hosting\/)\n\n[Systems Integration](https:\/\/www.endpointdev.com\/systems-integration\/)\n\n[Legacy Business Systems](https:\/\/www.endpointdev.com\/legacy-business-systems\/)\n\n[Security & Compliance](https:\/\/www.endpointdev.com\/security-and-compliance\/)\n\n[GIS](https:\/\/www.endpointdev.com\/gis\/)\n***\n[Expertise](https:\/\/www.endpointdev.com\/expertise\/)\n***\n[About Us](https:\/\/www.endpointdev.com\/about\/)\n\n[Our Team](https:\/\/www.endpointdev.com\/team\/)\n\n[Clients](https:\/\/www.endpointdev.com\/clients\/)\n\n[Blog](https:\/\/www.endpointdev.com\/blog\/)\n\n[Careers](https:\/\/www.endpointdev.com\/careers\/)\n***\n[VisionPort](https:\/\/www.visionport.com\/)\n***\n[Contact](https:\/\/www.endpointdev.com\/contact\/)\n\n[End Point Dev](https:\/\/www.endpointdev.com\/)\n\n[Services](https:\/\/www.endpointdev.com\/)\n\n[Expertise](https:\/\/www.endpointdev.com\/expertise\/)\n\n[About](https:\/\/www.endpointdev.com\/about\/)\n\n[VisionPort](https:\/\/www.visionport.com\/)\n\n[Contact](https:\/\/www.endpointdev.com\/contact\/)\n\n[Custom Ecommerce](https:\/\/www.endpointdev.com\/custom-ecommerce\/)\n\n[Application Development](https:\/\/www.endpointdev.com\/application-development\/)\n\n[Database Consulting](https:\/\/www.endpointdev.com\/database-consulting\/)\n\n[Cloud Hosting](https:\/\/www.endpointdev.com\/cloud-hosting\/)\n\n[Systems Integration](https:\/\/www.endpointdev.com\/systems-integration\/)\n\n[Legacy Business Systems](https:\/\/www.endpointdev.com\/legacy-business-systems\/)\n\n[Security & Compliance](https:\/\/www.endpointdev.com\/security-and-compliance\/)\n\n[GIS](https:\/\/www.endpointdev.com\/gis\/)\n\n### DevOps \/ Cloud\n- [AI Portal](https:\/\/www.endpointdev.com\/expertise\/ai-portal\/)\n- [AI Tools](https:\/\/www.endpointdev.com\/expertise\/ai-tools\/)\n- [Containers & Virtualization](https:\/\/www.endpointdev.com\/expertise\/containers-virtualization\/)\n- [Deployment Automation](https:\/\/www.endpointdev.com\/expertise\/chef-ansible-puppet\/)\n- [Hosting, Monitoring, and 24x7 Support](https:\/\/www.endpointdev.com\/expertise\/hosting-monitoring\/)\n- [Linux Systems](https:\/\/www.endpointdev.com\/expertise\/linux-systems\/)\n- [Remote Monitoring & Management](https:\/\/www.endpointdev.com\/expertise\/rmm\/)\n- [ROS, Robotics, Embedded Systems](https:\/\/www.endpointdev.com\/expertise\/robotics-embedded-systems\/)\n- [Security, Encryption, Vulnerability Mitigation](https:\/\/www.endpointdev.com\/expertise\/security-encryption\/)\n- [Version Control & DevCamps](https:\/\/www.endpointdev.com\/expertise\/version-control-devcamps\/)\n- [Windows Systems](https:\/\/www.endpointdev.com\/expertise\/windows-systems\/)\n\n### Databases\n- [Benchmarking](https:\/\/www.endpointdev.com\/expertise\/benchmarking\/)\n- [Database Migrations](https:\/\/www.endpointdev.com\/expertise\/migrations\/)\n- [Microsoft SQL Server](https:\/\/www.endpointdev.com\/expertise\/sqlserver\/)\n- [MySQL](https:\/\/www.endpointdev.com\/expertise\/mysql\/)\n- [NoSQL](https:\/\/www.endpointdev.com\/expertise\/nosql\/)\n- [On-site Training and Support](https:\/\/www.endpointdev.com\/expertise\/training-support\/)\n- [PostgreSQL](https:\/\/www.endpointdev.com\/expertise\/postgresql\/)\n- [Replication & Bucardo](https:\/\/www.endpointdev.com\/expertise\/replication\/)\n- [Support and Maintenance Packages](https:\/\/www.endpointdev.com\/expertise\/support-maintenance\/)\n\n### Frameworks\n- [Android & iOS Development](https:\/\/www.endpointdev.com\/expertise\/mobile\/)\n- [ASP, .NET, C\\#](https:\/\/www.endpointdev.com\/expertise\/dot-net\/)\n- [CMS (WordPress, Wix, Craft, custom)](https:\/\/www.endpointdev.com\/expertise\/cms\/)\n- [Django & Python](https:\/\/www.endpointdev.com\/expertise\/django-python\/)\n- [Elasticsearch, Solr](https:\/\/www.endpointdev.com\/expertise\/search\/)\n- [Geographic Information Systems](https:\/\/www.endpointdev.com\/expertise\/gis\/)\n- [Java](https:\/\/www.endpointdev.com\/expertise\/java\/)\n- [JavaScript](https:\/\/www.endpointdev.com\/expertise\/javascript\/)\n- [PHP](https:\/\/www.endpointdev.com\/expertise\/php\/)\n- [Ruby on Rails](https:\/\/www.endpointdev.com\/expertise\/ruby-on-rails\/)\n\n### Ecommerce\n- [End Point Ecommerce](https:\/\/www.endpointdev.com\/expertise\/end-point-ecommerce\/)\n- [APIs and Integrations](https:\/\/www.endpointdev.com\/expertise\/apis\/)\n- [Magento](https:\/\/www.endpointdev.com\/expertise\/magento\/)\n- [Payment Processing](https:\/\/www.endpointdev.com\/expertise\/payment\/)\n- [Perl & Interchange](https:\/\/www.endpointdev.com\/expertise\/perl-interchange\/)\n- [Responsive Design](https:\/\/www.endpointdev.com\/expertise\/responsive-design\/)\n- [SEO, Google Ads, Analytics](https:\/\/www.endpointdev.com\/expertise\/analytics\/)\n- [Spree and Solidus](https:\/\/www.endpointdev.com\/expertise\/spree-solidus\/)\n\n[About Us We design and build custom software solutions.](https:\/\/www.endpointdev.com\/about\/)\n\n[Our Team We’re software developers, design thinkers, and security experts.](https:\/\/www.endpointdev.com\/team\/)\n\n[Clients Since 1995 we’ve built our reputation by bringing expertise and care to your projects.](https:\/\/www.endpointdev.com\/clients\/)\n\n[Blog Ongoing observations by End Point Dev people](https:\/\/www.endpointdev.com\/blog\/)\n\n[Careers We currently have no open positions, but check back soon\\!](https:\/\/www.endpointdev.com\/careers\/)\n\n[Our Blog](https:\/\/www.endpointdev.com\/blog\/)\n\n[![](https:\/\/www.endpointdev.com\/images\/icons\/rss.svg)](https:\/\/www.endpointdev.com\/blog\/feed.xml)\n\n[Search]() [LLM expanded search]()\n\n***\n[Hide search results](https:\/\/www.endpointdev.com\/blog\/2012\/06\/moving-commit-to-another-branch-in-git\/)\n\n## Moving a Commit to Another Branch in Git\n[![Mike Farmer](https:\/\/www.endpointdev.com\/images\/people\/teampage\/mike-farmer.webp)](https:\/\/www.endpointdev.com\/blog\/authors\/mike-farmer\/)\n\nBy [Mike Farmer](https:\/\/www.endpointdev.com\/blog\/authors\/mike-farmer\/)   \n June 21, 2012\n\nPerhaps you’ve made the same mistake I have. You’re right in the middle of developing a feature when a request comes up to fix a different completely unrelated problem. So, you jump right in and fix the issue and then you realize you forgot to start a new git feature branch. Suddenly you realize that you need to merge just the fix you made, but don’t want to merge the commits from the previous feature your working on.\n\nGit rocks at manipulating branches and I knew this, but I wasn’t sure how to just move one commit to the master branch. After some digging and a little trial and error, I finally figured it out. This may not be the simplest approach, but it worked for me and wanted to share.\n\nThe branches I’ll be working with are master and feature. In the current scenario, the feature branch is 4 commits ahead of the master and the branch that I want to bring over is just the most recent.\n\nFirst things first, I need to ensure my master branch is up to date.\n```\ngit checkout master\ngit pull origin master\n```\nThen I’ll checkout my feature branch and make sure it’s completely up to date with the master branch.\n```\ngit checkout feature\ngit rebase origin\/master\n```\nNext, I’ll create a temporary feature branch that I’ll use later on to bring over the commit that I want.\n```\ngit checkout -b feature_tmp\n```\nI’ll do the same for master so that I can perform my merging and rebasing in isolation from the master branch.\n```\ngit checkout master\ngit checkout -b master_tmp\n```\nNow I’m going to merge the two tmp branches so that I have a history that contains all of my commits. This will give me the history that I want, but will include the 3 commits I don’t want.\n```\ngit merge feature_tmp\n```\nHere’s where the magic happens. I’m going to rebase this branch using interactive mode. I want to rebase everything back to the last commit on the master branch. For simplicity in the commands here, we’ll just use SHA-MASTER in place of the actual SHA1 hash.\n```\ngit rebase -i SHA-MASTER\n```\nThis loads the commits into my editor and from here I just delete the 3 commits that I didn’t want on my master branch. This will give me the history I want with the 4th commit coming right after the last commit on the master branch. After deleting the commits, I just save and quit my editor.\n\nNext, I merge my tmp branch into the master branch.\n```\ngit checkout master\ngit merge master_tmp\ngit log\n```\nNow in the log, I can see the history is in the correct order, just how I wanted it. To finish things up, I’ll just push my changes and then rebase my feature branch which will reorder my commits to match the master branch and place my feature commits as the last three commits in the log.\n```\ngit push origin master\ngit checkout feature\ngit rebase origin\/master\ngit log\n```\nThe last thing to do is delete my tmp branches.\n```\ngit branch -D tmp_master\ngit branch -D tmp_feature\n```\n[git](https:\/\/www.endpointdev.com\/blog\/tags\/git\/)\n***\n## Comments\nVisit the [GitHub issue](https:\/\/github.com\/EndPointCorp\/end-point-blog\/issues\/655) to view and write comments.\n\n### Popular Tags\n- [postgres 305](https:\/\/www.endpointdev.com\/blog\/tags\/postgres\/)\n- [rails 267](https:\/\/www.endpointdev.com\/blog\/tags\/rails\/)\n- [conference 194](https:\/\/www.endpointdev.com\/blog\/tags\/conference\/)\n- [database 179](https:\/\/www.endpointdev.com\/blog\/tags\/database\/)\n- [ruby 166](https:\/\/www.endpointdev.com\/blog\/tags\/ruby\/)\n- [ecommerce 162](https:\/\/www.endpointdev.com\/blog\/tags\/ecommerce\/)\n- [javascript 148](https:\/\/www.endpointdev.com\/blog\/tags\/javascript\/)\n- [visionport 144](https:\/\/www.endpointdev.com\/blog\/tags\/visionport\/)\n- [perl 117](https:\/\/www.endpointdev.com\/blog\/tags\/perl\/)\n- [open-source 115](https:\/\/www.endpointdev.com\/blog\/tags\/open-source\/)\n- [sysadmin 106](https:\/\/www.endpointdev.com\/blog\/tags\/sysadmin\/)\n- [tips 106](https:\/\/www.endpointdev.com\/blog\/tags\/tips\/)\n\n- [All Tags](https:\/\/www.endpointdev.com\/blog\/tags\/)\n***\n### Archive\n- [Posts by date](https:\/\/www.endpointdev.com\/blog\/archive\/)\n- [Posts by author](https:\/\/www.endpointdev.com\/blog\/authors\/)\n\n- [Services](https:\/\/www.endpointdev.com\/)\n- [Custom Ecommerce](https:\/\/www.endpointdev.com\/custom-ecommerce\/)\n- [Application Development](https:\/\/www.endpointdev.com\/application-development\/)\n- [Database Consulting](https:\/\/www.endpointdev.com\/database-consulting\/)\n- [Cloud Hosting](https:\/\/www.endpointdev.com\/cloud-hosting\/)\n- [Systems Integration](https:\/\/www.endpointdev.com\/systems-integration\/)\n- [Legacy Business Systems](https:\/\/www.endpointdev.com\/legacy-business-systems\/)\n- [Security & Compliance](https:\/\/www.endpointdev.com\/security-and-compliance\/)\n- [GIS](https:\/\/www.endpointdev.com\/gis\/)\n\n- [Expertise](https:\/\/www.endpointdev.com\/expertise\/)\n- [DevOps \/ Cloud](https:\/\/www.endpointdev.com\/expertise\/#devops-cloud)\n- [Databases](https:\/\/www.endpointdev.com\/expertise\/#databases)\n- [Frameworks](https:\/\/www.endpointdev.com\/expertise\/#frameworks)\n- [Ecommerce](https:\/\/www.endpointdev.com\/expertise\/#ecommerce)\n\n- [About](https:\/\/www.endpointdev.com\/about\/)\n- [Our Team](https:\/\/www.endpointdev.com\/team\/)\n- [Clients](https:\/\/www.endpointdev.com\/clients\/)\n- [Blog](https:\/\/www.endpointdev.com\/blog\/)\n- [Careers](https:\/\/www.endpointdev.com\/careers\/)\n\n- [VisionPort](https:\/\/www.visionport.com\/)\n\n- [Contact](https:\/\/www.endpointdev.com\/contact\/)\n\n[![](https:\/\/www.endpointdev.com\/images\/icons\/linkedin.png)](https:\/\/www.linkedin.com\/company\/end-point-corporation)  [![](https:\/\/www.endpointdev.com\/images\/icons\/x-end-point-blue.svg)](https:\/\/x.com\/endpointdev)  [![](https:\/\/www.endpointdev.com\/images\/icons\/instagram-end-point-blue.svg)](https:\/\/instagram.com\/endpointcorporation)\n\n© 2026 End Point Corporation","attrs_readable_markdown":"Perhaps you’ve made the same mistake I have. You’re right in the middle of developing a feature when a request comes up to fix a different completely unrelated problem. So, you jump right in and fix the issue and then you realize you forgot to start a new git feature branch. Suddenly you realize that you need to merge just the fix you made, but don’t want to merge the commits from the previous feature your working on.\n\nGit rocks at manipulating branches and I knew this, but I wasn’t sure how to just move one commit to the master branch. After some digging and a little trial and error, I finally figured it out. This may not be the simplest approach, but it worked for me and wanted to share.\n\nThe branches I’ll be working with are master and feature. In the current scenario, the feature branch is 4 commits ahead of the master and the branch that I want to bring over is just the most recent.\n\nFirst things first, I need to ensure my master branch is up to date.\n```\ngit checkout master\ngit pull origin master\n```\nThen I’ll checkout my feature branch and make sure it’s completely up to date with the master branch.\n```\ngit checkout feature\ngit rebase origin\/master\n```\nNext, I’ll create a temporary feature branch that I’ll use later on to bring over the commit that I want.\n```\ngit checkout -b feature_tmp\n```\nI’ll do the same for master so that I can perform my merging and rebasing in isolation from the master branch.\n```\ngit checkout master\ngit checkout -b master_tmp\n```\nNow I’m going to merge the two tmp branches so that I have a history that contains all of my commits. This will give me the history that I want, but will include the 3 commits I don’t want.\n```\ngit merge feature_tmp\n```\nHere’s where the magic happens. I’m going to rebase this branch using interactive mode. I want to rebase everything back to the last commit on the master branch. For simplicity in the commands here, we’ll just use SHA-MASTER in place of the actual SHA1 hash.\n```\ngit rebase -i SHA-MASTER\n```\nThis loads the commits into my editor and from here I just delete the 3 commits that I didn’t want on my master branch. This will give me the history I want with the 4th commit coming right after the last commit on the master branch. After deleting the commits, I just save and quit my editor.\n\nNext, I merge my tmp branch into the master branch.\n```\ngit checkout master\ngit merge master_tmp\ngit log\n```\nNow in the log, I can see the history is in the correct order, just how I wanted it. To finish things up, I’ll just push my changes and then rebase my feature branch which will reorder my commits to match the master branch and place my feature commits as the last three commits in the log.\n```\ngit push origin master\ngit checkout feature\ngit rebase origin\/master\ngit log\n```\nThe last thing to do is delete my tmp branches.\n```\ngit branch -D tmp_master\ngit branch -D tmp_feature\n```\n[git](https:\/\/www.endpointdev.com\/blog\/tags\/git\/)\n***","meta_canonical":null,"ml_categories_json":"","ml_types_json":"","ml_intent_types_json":"","meta_language":"en","attrs_author":null,"attrs_publish_time":0,"attrs_original_publish_time":1338508800,"attrs_is_republished":0,"attrs_nr_words":"859","attrs_boilerpipe_nr_words":"520","body_ext_links_number":6,"body_int_links_number":72,"meta_nofollow":0,"meta_noarchive":0,"props_was_rendered":0,"src_redirect":"","download_time_msec":82,"download_ttfb_msec":81,"download_size":6921}

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.endpointdev.com/blog/2012/06/moving-commit-to-another-branch-in-git/
Last Crawled	2026-04-15 21:03:49 (8 days ago)
First Indexed	2021-10-22 22:18:23 (4 years ago)
HTTP Status Code	200
Content
Meta Title	Moving a Commit to Another Branch in Git \| End Point Dev
Meta Description	null
Meta Canonical	null
Boilerpipe Text	Perhaps you’ve made the same mistake I have. You’re right in the middle of developing a feature when a request comes up to fix a different completely unrelated problem. So, you jump right in and fix the issue and then you realize you forgot to start a new git feature branch. Suddenly you realize that you need to merge just the fix you made, but don’t want to merge the commits from the previous feature your working on. Git rocks at manipulating branches and I knew this, but I wasn’t sure how to just move one commit to the master branch. After some digging and a little trial and error, I finally figured it out. This may not be the simplest approach, but it worked for me and wanted to share. The branches I’ll be working with are master and feature. In the current scenario, the feature branch is 4 commits ahead of the master and the branch that I want to bring over is just the most recent. First things first, I need to ensure my master branch is up to date. git checkout master git pull origin master Then I’ll checkout my feature branch and make sure it’s completely up to date with the master branch. git checkout feature git rebase origin/master Next, I’ll create a temporary feature branch that I’ll use later on to bring over the commit that I want. git checkout -b feature_tmp I’ll do the same for master so that I can perform my merging and rebasing in isolation from the master branch. git checkout master git checkout -b master_tmp Now I’m going to merge the two tmp branches so that I have a history that contains all of my commits. This will give me the history that I want, but will include the 3 commits I don’t want. git merge feature_tmp Here’s where the magic happens. I’m going to rebase this branch using interactive mode. I want to rebase everything back to the last commit on the master branch. For simplicity in the commands here, we’ll just use SHA-MASTER in place of the actual SHA1 hash. git rebase -i SHA-MASTER This loads the commits into my editor and from here I just delete the 3 commits that I didn’t want on my master branch. This will give me the history I want with the 4th commit coming right after the last commit on the master branch. After deleting the commits, I just save and quit my editor. Next, I merge my tmp branch into the master branch. git checkout master git merge master_tmp git log Now in the log, I can see the history is in the correct order, just how I wanted it. To finish things up, I’ll just push my changes and then rebase my feature branch which will reorder my commits to match the master branch and place my feature commits as the last three commits in the log. git push origin master git checkout feature git rebase origin/master git log The last thing to do is delete my tmp branches. git branch -D tmp_master git branch -D tmp_feature git
Markdown	[Skip to content](https://www.endpointdev.com/blog/2012/06/moving-commit-to-another-branch-in-git/#main-content) × [Home](https://www.endpointdev.com/) * [Custom Ecommerce](https://www.endpointdev.com/custom-ecommerce/) [Application Development](https://www.endpointdev.com/application-development/) [Database Consulting](https://www.endpointdev.com/database-consulting/) [Cloud Hosting](https://www.endpointdev.com/cloud-hosting/) [Systems Integration](https://www.endpointdev.com/systems-integration/) [Legacy Business Systems](https://www.endpointdev.com/legacy-business-systems/) [Security & Compliance](https://www.endpointdev.com/security-and-compliance/) [GIS](https://www.endpointdev.com/gis/) * [Expertise](https://www.endpointdev.com/expertise/) * [About Us](https://www.endpointdev.com/about/) [Our Team](https://www.endpointdev.com/team/) [Clients](https://www.endpointdev.com/clients/) [Blog](https://www.endpointdev.com/blog/) [Careers](https://www.endpointdev.com/careers/) * [VisionPort](https://www.visionport.com/) * [Contact](https://www.endpointdev.com/contact/) [End Point Dev](https://www.endpointdev.com/) [Services](https://www.endpointdev.com/) [Expertise](https://www.endpointdev.com/expertise/) [About](https://www.endpointdev.com/about/) [VisionPort](https://www.visionport.com/) [Contact](https://www.endpointdev.com/contact/) [Custom Ecommerce](https://www.endpointdev.com/custom-ecommerce/) [Application Development](https://www.endpointdev.com/application-development/) [Database Consulting](https://www.endpointdev.com/database-consulting/) [Cloud Hosting](https://www.endpointdev.com/cloud-hosting/) [Systems Integration](https://www.endpointdev.com/systems-integration/) [Legacy Business Systems](https://www.endpointdev.com/legacy-business-systems/) [Security & Compliance](https://www.endpointdev.com/security-and-compliance/) [GIS](https://www.endpointdev.com/gis/) ### DevOps / Cloud - [AI Portal](https://www.endpointdev.com/expertise/ai-portal/) - [AI Tools](https://www.endpointdev.com/expertise/ai-tools/) - [Containers & Virtualization](https://www.endpointdev.com/expertise/containers-virtualization/) - [Deployment Automation](https://www.endpointdev.com/expertise/chef-ansible-puppet/) - [Hosting, Monitoring, and 24x7 Support](https://www.endpointdev.com/expertise/hosting-monitoring/) - [Linux Systems](https://www.endpointdev.com/expertise/linux-systems/) - [Remote Monitoring & Management](https://www.endpointdev.com/expertise/rmm/) - [ROS, Robotics, Embedded Systems](https://www.endpointdev.com/expertise/robotics-embedded-systems/) - [Security, Encryption, Vulnerability Mitigation](https://www.endpointdev.com/expertise/security-encryption/) - [Version Control & DevCamps](https://www.endpointdev.com/expertise/version-control-devcamps/) - [Windows Systems](https://www.endpointdev.com/expertise/windows-systems/) ### Databases - [Benchmarking](https://www.endpointdev.com/expertise/benchmarking/) - [Database Migrations](https://www.endpointdev.com/expertise/migrations/) - [Microsoft SQL Server](https://www.endpointdev.com/expertise/sqlserver/) - [MySQL](https://www.endpointdev.com/expertise/mysql/) - [NoSQL](https://www.endpointdev.com/expertise/nosql/) - [On-site Training and Support](https://www.endpointdev.com/expertise/training-support/) - [PostgreSQL](https://www.endpointdev.com/expertise/postgresql/) - [Replication & Bucardo](https://www.endpointdev.com/expertise/replication/) - [Support and Maintenance Packages](https://www.endpointdev.com/expertise/support-maintenance/) ### Frameworks - [Android & iOS Development](https://www.endpointdev.com/expertise/mobile/) - [ASP, .NET, C\#](https://www.endpointdev.com/expertise/dot-net/) - [CMS (WordPress, Wix, Craft, custom)](https://www.endpointdev.com/expertise/cms/) - [Django & Python](https://www.endpointdev.com/expertise/django-python/) - [Elasticsearch, Solr](https://www.endpointdev.com/expertise/search/) - [Geographic Information Systems](https://www.endpointdev.com/expertise/gis/) - [Java](https://www.endpointdev.com/expertise/java/) - [JavaScript](https://www.endpointdev.com/expertise/javascript/) - [PHP](https://www.endpointdev.com/expertise/php/) - [Ruby on Rails](https://www.endpointdev.com/expertise/ruby-on-rails/) ### Ecommerce - [End Point Ecommerce](https://www.endpointdev.com/expertise/end-point-ecommerce/) - [APIs and Integrations](https://www.endpointdev.com/expertise/apis/) - [Magento](https://www.endpointdev.com/expertise/magento/) - [Payment Processing](https://www.endpointdev.com/expertise/payment/) - [Perl & Interchange](https://www.endpointdev.com/expertise/perl-interchange/) - [Responsive Design](https://www.endpointdev.com/expertise/responsive-design/) - [SEO, Google Ads, Analytics](https://www.endpointdev.com/expertise/analytics/) - [Spree and Solidus](https://www.endpointdev.com/expertise/spree-solidus/) [About Us We design and build custom software solutions.](https://www.endpointdev.com/about/) [Our Team We’re software developers, design thinkers, and security experts.](https://www.endpointdev.com/team/) [Clients Since 1995 we’ve built our reputation by bringing expertise and care to your projects.](https://www.endpointdev.com/clients/) [Blog Ongoing observations by End Point Dev people](https://www.endpointdev.com/blog/) [Careers We currently have no open positions, but check back soon\!](https://www.endpointdev.com/careers/) [Our Blog](https://www.endpointdev.com/blog/) [![](https://www.endpointdev.com/images/icons/rss.svg)](https://www.endpointdev.com/blog/feed.xml) [Search]() [LLM expanded search]() * [Hide search results](https://www.endpointdev.com/blog/2012/06/moving-commit-to-another-branch-in-git/) ## Moving a Commit to Another Branch in Git [![Mike Farmer](https://www.endpointdev.com/images/people/teampage/mike-farmer.webp)](https://www.endpointdev.com/blog/authors/mike-farmer/) By [Mike Farmer](https://www.endpointdev.com/blog/authors/mike-farmer/) June 21, 2012 Perhaps you’ve made the same mistake I have. You’re right in the middle of developing a feature when a request comes up to fix a different completely unrelated problem. So, you jump right in and fix the issue and then you realize you forgot to start a new git feature branch. Suddenly you realize that you need to merge just the fix you made, but don’t want to merge the commits from the previous feature your working on. Git rocks at manipulating branches and I knew this, but I wasn’t sure how to just move one commit to the master branch. After some digging and a little trial and error, I finally figured it out. This may not be the simplest approach, but it worked for me and wanted to share. The branches I’ll be working with are master and feature. In the current scenario, the feature branch is 4 commits ahead of the master and the branch that I want to bring over is just the most recent. First things first, I need to ensure my master branch is up to date. ``` git checkout master git pull origin master ``` Then I’ll checkout my feature branch and make sure it’s completely up to date with the master branch. ``` git checkout feature git rebase origin/master ``` Next, I’ll create a temporary feature branch that I’ll use later on to bring over the commit that I want. ``` git checkout -b feature_tmp ``` I’ll do the same for master so that I can perform my merging and rebasing in isolation from the master branch. ``` git checkout master git checkout -b master_tmp ``` Now I’m going to merge the two tmp branches so that I have a history that contains all of my commits. This will give me the history that I want, but will include the 3 commits I don’t want. ``` git merge feature_tmp ``` Here’s where the magic happens. I’m going to rebase this branch using interactive mode. I want to rebase everything back to the last commit on the master branch. For simplicity in the commands here, we’ll just use SHA-MASTER in place of the actual SHA1 hash. ``` git rebase -i SHA-MASTER ``` This loads the commits into my editor and from here I just delete the 3 commits that I didn’t want on my master branch. This will give me the history I want with the 4th commit coming right after the last commit on the master branch. After deleting the commits, I just save and quit my editor. Next, I merge my tmp branch into the master branch. ``` git checkout master git merge master_tmp git log ``` Now in the log, I can see the history is in the correct order, just how I wanted it. To finish things up, I’ll just push my changes and then rebase my feature branch which will reorder my commits to match the master branch and place my feature commits as the last three commits in the log. ``` git push origin master git checkout feature git rebase origin/master git log ``` The last thing to do is delete my tmp branches. ``` git branch -D tmp_master git branch -D tmp_feature ``` [git](https://www.endpointdev.com/blog/tags/git/) * ## Comments Visit the [GitHub issue](https://github.com/EndPointCorp/end-point-blog/issues/655) to view and write comments. ### Popular Tags - [postgres 305](https://www.endpointdev.com/blog/tags/postgres/) - [rails 267](https://www.endpointdev.com/blog/tags/rails/) - [conference 194](https://www.endpointdev.com/blog/tags/conference/) - [database 179](https://www.endpointdev.com/blog/tags/database/) - [ruby 166](https://www.endpointdev.com/blog/tags/ruby/) - [ecommerce 162](https://www.endpointdev.com/blog/tags/ecommerce/) - [javascript 148](https://www.endpointdev.com/blog/tags/javascript/) - [visionport 144](https://www.endpointdev.com/blog/tags/visionport/) - [perl 117](https://www.endpointdev.com/blog/tags/perl/) - [open-source 115](https://www.endpointdev.com/blog/tags/open-source/) - [sysadmin 106](https://www.endpointdev.com/blog/tags/sysadmin/) - [tips 106](https://www.endpointdev.com/blog/tags/tips/) - [All Tags](https://www.endpointdev.com/blog/tags/) * ### Archive - [Posts by date](https://www.endpointdev.com/blog/archive/) - [Posts by author](https://www.endpointdev.com/blog/authors/) - [Services](https://www.endpointdev.com/) - [Custom Ecommerce](https://www.endpointdev.com/custom-ecommerce/) - [Application Development](https://www.endpointdev.com/application-development/) - [Database Consulting](https://www.endpointdev.com/database-consulting/) - [Cloud Hosting](https://www.endpointdev.com/cloud-hosting/) - [Systems Integration](https://www.endpointdev.com/systems-integration/) - [Legacy Business Systems](https://www.endpointdev.com/legacy-business-systems/) - [Security & Compliance](https://www.endpointdev.com/security-and-compliance/) - [GIS](https://www.endpointdev.com/gis/) - [Expertise](https://www.endpointdev.com/expertise/) - [DevOps / Cloud](https://www.endpointdev.com/expertise/#devops-cloud) - [Databases](https://www.endpointdev.com/expertise/#databases) - [Frameworks](https://www.endpointdev.com/expertise/#frameworks) - [Ecommerce](https://www.endpointdev.com/expertise/#ecommerce) - [About](https://www.endpointdev.com/about/) - [Our Team](https://www.endpointdev.com/team/) - [Clients](https://www.endpointdev.com/clients/) - [Blog](https://www.endpointdev.com/blog/) - [Careers](https://www.endpointdev.com/careers/) - [VisionPort](https://www.visionport.com/) - [Contact](https://www.endpointdev.com/contact/) [![](https://www.endpointdev.com/images/icons/linkedin.png)](https://www.linkedin.com/company/end-point-corporation) [![](https://www.endpointdev.com/images/icons/x-end-point-blue.svg)](https://x.com/endpointdev) [![](https://www.endpointdev.com/images/icons/instagram-end-point-blue.svg)](https://instagram.com/endpointcorporation) © 2026 End Point Corporation
Readable Markdown	Perhaps you’ve made the same mistake I have. You’re right in the middle of developing a feature when a request comes up to fix a different completely unrelated problem. So, you jump right in and fix the issue and then you realize you forgot to start a new git feature branch. Suddenly you realize that you need to merge just the fix you made, but don’t want to merge the commits from the previous feature your working on. Git rocks at manipulating branches and I knew this, but I wasn’t sure how to just move one commit to the master branch. After some digging and a little trial and error, I finally figured it out. This may not be the simplest approach, but it worked for me and wanted to share. The branches I’ll be working with are master and feature. In the current scenario, the feature branch is 4 commits ahead of the master and the branch that I want to bring over is just the most recent. First things first, I need to ensure my master branch is up to date. ``` git checkout master git pull origin master ``` Then I’ll checkout my feature branch and make sure it’s completely up to date with the master branch. ``` git checkout feature git rebase origin/master ``` Next, I’ll create a temporary feature branch that I’ll use later on to bring over the commit that I want. ``` git checkout -b feature_tmp ``` I’ll do the same for master so that I can perform my merging and rebasing in isolation from the master branch. ``` git checkout master git checkout -b master_tmp ``` Now I’m going to merge the two tmp branches so that I have a history that contains all of my commits. This will give me the history that I want, but will include the 3 commits I don’t want. ``` git merge feature_tmp ``` Here’s where the magic happens. I’m going to rebase this branch using interactive mode. I want to rebase everything back to the last commit on the master branch. For simplicity in the commands here, we’ll just use SHA-MASTER in place of the actual SHA1 hash. ``` git rebase -i SHA-MASTER ``` This loads the commits into my editor and from here I just delete the 3 commits that I didn’t want on my master branch. This will give me the history I want with the 4th commit coming right after the last commit on the master branch. After deleting the commits, I just save and quit my editor. Next, I merge my tmp branch into the master branch. ``` git checkout master git merge master_tmp git log ``` Now in the log, I can see the history is in the correct order, just how I wanted it. To finish things up, I’ll just push my changes and then rebase my feature branch which will reorder my commits to match the master branch and place my feature commits as the last three commits in the log. ``` git push origin master git checkout feature git rebase origin/master git log ``` The last thing to do is delete my tmp branches. ``` git branch -D tmp_master git branch -D tmp_feature ``` [git](https://www.endpointdev.com/blog/tags/git/) ***
ML Classification
ML Categories	null
ML Page Types	null
ML Intent Types	null
Content Metadata
Language	en
Author	null
Publish Time	not set
Original Publish Time	2012-06-01 00:00:00 (13 years ago)
Republished	No
Word Count (Total)	859
Word Count (Content)	520
Links
External Links	6
Internal Links	72
Technical SEO
Meta Nofollow	No
Meta Noarchive	No
JS Rendered	No
Redirect Target	null
Performance
Download Time (ms)	82
TTFB (ms)	81
Download Size (bytes)	6,921
Shard	67 (laksa)
Root Hash	15777514137560783467
Unparsed URL	com,endpointdev!www,/blog/2012/06/moving-commit-to-another-branch-in-git/ s443