🕷️ Crawler Inspector

URL Lookup

Direct Parameter Lookup

Raw Queries and Responses

1. Shard Calculation

Query:

Response:

Calculated Shard: 20 (from laksa171)

2. Crawled Status Check

Query:

curl -X POST \
  'http://laksa020.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.flother.is/til/git-move-commit-to-branch/\')), getAhrefsUnparsedNoserviceFromURL(\'https://www.flother.is/til/git-move-commit-to-branch/\'))) FORMAT JSONEachRow'

Response:

{"found_url":"https:\/\/www.flother.is\/til\/git-move-commit-to-branch\/","crawl_time":1775946171,"first_indexed_time":1677807460,"http_code":200,"src_unparsed":"is,flother!www,\/til\/git-move-commit-to-branch\/ s443","src_root_hash":"2267687846180591220","history_drop_reason":null,"meta_title":"How to move your most recent Git commit to a new branch — Flother","meta_descriptions":["Flother is the online home of Matt Riggott, a programmer and map-maker living in Reykjavík, Iceland."],"attrs_boilerpipe_text":"If you’re anything like me you’ll have found yourself writing new code and accidentally committing it to the default branch (usually\nmaster\nor\nmain\n). This might be alright for your personal repos, but when you’re working in a larger team and collaborating on a project using a branch-based workflow (like\nGitHub flow\n), then you need to move that commit to a new branch before you push the code.\nOne way to do this would be to ‘undo’ the commit: rewind your repository history so it’s as if that commit never happened, but with your local files still modified. However, if you do that, you lose the detailed commit message you spent ten minutes writing (you did write a good commit message, didn’t you?). No, what you want to do is create a new branch that includes your latest commit, and then remove the commit from your default branch.\nSo what you’ve done so far is commit your new code to the\nmaster\nbranch by accident:\ngit\ncommit\n#\nOops\nTo fix that, you should branch off from the tip of\nmaster\nand then move\nmaster\nback one commit:\ngit\nswitch\n-\nC\nnew-branch\ngit\nswitch master\ngit\nreset\n--\nsoft\nHEAD^\nThat last line,\ngit reset --soft HEAD^\n, will remove the last commit from\nmaster\nand the files you changed will still be modified but staged. (If you have more than one commit to remove, you can use\nHEAD~3\ninstead of\nHEAD^\n, where\n3\nis the number of commits you want to remove. You actually have\nloads of options available\n.)\nNow you’ve cleaned that up, you can unstage the modified files and then push the new branch:\ngit\nreset .\ngit\nswitch new-branch\ngit\npush\n-\nu\norigin new-branch\nAnd now no-one’s any the wiser. You have a clean\nmaster\nbranch, a new branch with your new code, and you’re free to carry on\nadding new commits to the branch\n.","attrs_markdown":"[Flother](https:\/\/www.flother.is\/)\n\n# How to move your most recent Git commit to a new branch\nToday I learnt …\n\n2 March 2023\n\nIf you’re anything like me you’ll have found yourself writing new code and accidentally committing it to the default branch (usually `master` or `main`). This might be alright for your personal repos, but when you’re working in a larger team and collaborating on a project using a branch-based workflow (like [GitHub flow](https:\/\/docs.github.com\/en\/get-started\/quickstart\/github-flow)), then you need to move that commit to a new branch before you push the code.\n\nOne way to do this would be to ‘undo’ the commit: rewind your repository history so it’s as if that commit never happened, but with your local files still modified. However, if you do that, you lose the detailed commit message you spent ten minutes writing (you did write a good commit message, didn’t you?). No, what you want to do is create a new branch that includes your latest commit, and then remove the commit from your default branch.\n\nSo what you’ve done so far is commit your new code to the `master` branch by accident:\n```\ngit commit # Oops\n```\nTo fix that, you should branch off from the tip of `master` and then move `master` back one commit:\n```\ngit switch -C new-branch\ngit switch master\ngit reset --soft HEAD^\n```\nThat last line, `git reset --soft HEAD^`, will remove the last commit from `master` and the files you changed will still be modified but staged. (If you have more than one commit to remove, you can use `HEAD~3` instead of `HEAD^`, where `3` is the number of commits you want to remove. You actually have [loads of options available](https:\/\/git-scm.com\/docs\/git-rev-parse#_specifying_revisions).)\n\nNow you’ve cleaned that up, you can unstage the modified files and then push the new branch:\n```\ngit reset .\ngit switch new-branch\ngit push -u origin new-branch\n```\nAnd now no-one’s any the wiser. You have a clean `master` branch, a new branch with your new code, and you’re free to carry on [adding new commits to the branch](https:\/\/xkcd.com\/1296\/).\n\n- [Git](https:\/\/www.flother.is\/tags\/git\/ \"See all pages tagged Git\")\n\n- [Home](https:\/\/www.flother.is\/)\n- [Blog](https:\/\/www.flother.is\/blog\/)\n- [Today I Learnt](https:\/\/www.flother.is\/til\/)\n- [Travelogue](https:\/\/www.flother.is\/travelogue\/)\n- [Podcast](https:\/\/www.flother.is\/podcast\/)\n- [Categories](https:\/\/www.flother.is\/categories\/)\n- [Tags](https:\/\/www.flother.is\/tags\/)\n\n- [GitHub](https:\/\/github.com\/flother)\n- [OpenStreetMap](https:\/\/www.openstreetmap.org\/user\/flother)\n- [Flickr](https:\/\/www.flickr.com\/photos\/riggott)\n\n© 2023","attrs_readable_markdown":"If you’re anything like me you’ll have found yourself writing new code and accidentally committing it to the default branch (usually `master` or `main`). This might be alright for your personal repos, but when you’re working in a larger team and collaborating on a project using a branch-based workflow (like [GitHub flow](https:\/\/docs.github.com\/en\/get-started\/quickstart\/github-flow)), then you need to move that commit to a new branch before you push the code.\n\nOne way to do this would be to ‘undo’ the commit: rewind your repository history so it’s as if that commit never happened, but with your local files still modified. However, if you do that, you lose the detailed commit message you spent ten minutes writing (you did write a good commit message, didn’t you?). No, what you want to do is create a new branch that includes your latest commit, and then remove the commit from your default branch.\n\nSo what you’ve done so far is commit your new code to the `master` branch by accident:\n```\ngit commit # Oops\n```\nTo fix that, you should branch off from the tip of `master` and then move `master` back one commit:\n```\ngit switch -C new-branch\ngit switch master\ngit reset --soft HEAD^\n```\nThat last line, `git reset --soft HEAD^`, will remove the last commit from `master` and the files you changed will still be modified but staged. (If you have more than one commit to remove, you can use `HEAD~3` instead of `HEAD^`, where `3` is the number of commits you want to remove. You actually have [loads of options available](https:\/\/git-scm.com\/docs\/git-rev-parse#_specifying_revisions).)\n\nNow you’ve cleaned that up, you can unstage the modified files and then push the new branch:\n```\ngit reset .\ngit switch new-branch\ngit push -u origin new-branch\n```\nAnd now no-one’s any the wiser. You have a clean `master` branch, a new branch with your new code, and you’re free to carry on [adding new commits to the branch](https:\/\/xkcd.com\/1296\/).","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

9 hours ago

🤖

ROBOTS ALLOWED

Page Info Filters

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

Page Details

Property	Value
URL	https://www.flother.is/til/git-move-commit-to-branch/
Last Crawled	2026-04-11 22:22:51 (9 hours ago)
First Indexed	2023-03-03 01:37:40 (3 years ago)
HTTP Status Code	200
Meta Title	How to move your most recent Git commit to a new branch — Flother
Meta Description	Flother is the online home of Matt Riggott, a programmer and map-maker living in Reykjavík, Iceland.
Meta Canonical	null
Boilerpipe Text	If you’re anything like me you’ll have found yourself writing new code and accidentally committing it to the default branch (usually master or main ). This might be alright for your personal repos, but when you’re working in a larger team and collaborating on a project using a branch-based workflow (like GitHub flow ), then you need to move that commit to a new branch before you push the code. One way to do this would be to ‘undo’ the commit: rewind your repository history so it’s as if that commit never happened, but with your local files still modified. However, if you do that, you lose the detailed commit message you spent ten minutes writing (you did write a good commit message, didn’t you?). No, what you want to do is create a new branch that includes your latest commit, and then remove the commit from your default branch. So what you’ve done so far is commit your new code to the master branch by accident: git commit # Oops To fix that, you should branch off from the tip of master and then move master back one commit: git switch - C new-branch git switch master git reset -- soft HEAD^ That last line, git reset --soft HEAD^ , will remove the last commit from master and the files you changed will still be modified but staged. (If you have more than one commit to remove, you can use HEAD~3 instead of HEAD^ , where 3 is the number of commits you want to remove. You actually have loads of options available .) Now you’ve cleaned that up, you can unstage the modified files and then push the new branch: git reset . git switch new-branch git push - u origin new-branch And now no-one’s any the wiser. You have a clean master branch, a new branch with your new code, and you’re free to carry on adding new commits to the branch .
Markdown	[Flother](https://www.flother.is/) # How to move your most recent Git commit to a new branch Today I learnt … 2 March 2023 If you’re anything like me you’ll have found yourself writing new code and accidentally committing it to the default branch (usually `master` or `main`). This might be alright for your personal repos, but when you’re working in a larger team and collaborating on a project using a branch-based workflow (like [GitHub flow](https://docs.github.com/en/get-started/quickstart/github-flow)), then you need to move that commit to a new branch before you push the code. One way to do this would be to ‘undo’ the commit: rewind your repository history so it’s as if that commit never happened, but with your local files still modified. However, if you do that, you lose the detailed commit message you spent ten minutes writing (you did write a good commit message, didn’t you?). No, what you want to do is create a new branch that includes your latest commit, and then remove the commit from your default branch. So what you’ve done so far is commit your new code to the `master` branch by accident: ``` git commit # Oops ``` To fix that, you should branch off from the tip of `master` and then move `master` back one commit: ``` git switch -C new-branch git switch master git reset --soft HEAD^ ``` That last line, `git reset --soft HEAD^`, will remove the last commit from `master` and the files you changed will still be modified but staged. (If you have more than one commit to remove, you can use `HEAD~3` instead of `HEAD^`, where `3` is the number of commits you want to remove. You actually have [loads of options available](https://git-scm.com/docs/git-rev-parse#_specifying_revisions).) Now you’ve cleaned that up, you can unstage the modified files and then push the new branch: ``` git reset . git switch new-branch git push -u origin new-branch ``` And now no-one’s any the wiser. You have a clean `master` branch, a new branch with your new code, and you’re free to carry on [adding new commits to the branch](https://xkcd.com/1296/). - [Git](https://www.flother.is/tags/git/ "See all pages tagged Git") - [Home](https://www.flother.is/) - [Blog](https://www.flother.is/blog/) - [Today I Learnt](https://www.flother.is/til/) - [Travelogue](https://www.flother.is/travelogue/) - [Podcast](https://www.flother.is/podcast/) - [Categories](https://www.flother.is/categories/) - [Tags](https://www.flother.is/tags/) - [GitHub](https://github.com/flother) - [OpenStreetMap](https://www.openstreetmap.org/user/flother) - [Flickr](https://www.flickr.com/photos/riggott) © 2023
Readable Markdown	If you’re anything like me you’ll have found yourself writing new code and accidentally committing it to the default branch (usually `master` or `main`). This might be alright for your personal repos, but when you’re working in a larger team and collaborating on a project using a branch-based workflow (like [GitHub flow](https://docs.github.com/en/get-started/quickstart/github-flow)), then you need to move that commit to a new branch before you push the code. One way to do this would be to ‘undo’ the commit: rewind your repository history so it’s as if that commit never happened, but with your local files still modified. However, if you do that, you lose the detailed commit message you spent ten minutes writing (you did write a good commit message, didn’t you?). No, what you want to do is create a new branch that includes your latest commit, and then remove the commit from your default branch. So what you’ve done so far is commit your new code to the `master` branch by accident: ``` git commit # Oops ``` To fix that, you should branch off from the tip of `master` and then move `master` back one commit: ``` git switch -C new-branch git switch master git reset --soft HEAD^ ``` That last line, `git reset --soft HEAD^`, will remove the last commit from `master` and the files you changed will still be modified but staged. (If you have more than one commit to remove, you can use `HEAD~3` instead of `HEAD^`, where `3` is the number of commits you want to remove. You actually have [loads of options available](https://git-scm.com/docs/git-rev-parse#_specifying_revisions).) Now you’ve cleaned that up, you can unstage the modified files and then push the new branch: ``` git reset . git switch new-branch git push -u origin new-branch ``` And now no-one’s any the wiser. You have a clean `master` branch, a new branch with your new code, and you’re free to carry on [adding new commits to the branch](https://xkcd.com/1296/).
Shard	20 (laksa)
Root Hash	2267687846180591220
Unparsed URL	is,flother!www,/til/git-move-commit-to-branch/ s443