🕷️ Crawler Inspector

URL Lookup

Direct Parameter Lookup

Raw Queries and Responses

1. Shard Calculation

Query:

Response:

Calculated Shard: 54 (from laksa087)

2. Crawled Status Check

Query:

curl -X POST \
  'http://laksa054.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://git-scm.com/docs/git-cherry-pick\')), getAhrefsUnparsedNoserviceFromURL(\'https://git-scm.com/docs/git-cherry-pick\'))) FORMAT JSONEachRow'

Response:

{"found_url":"https:\/\/git-scm.com\/docs\/git-cherry-pick","crawl_time":1775862938,"first_indexed_time":1376013967,"http_code":200,"src_unparsed":"com,git-scm!\/docs\/git-cherry-pick s443","src_root_hash":"7104038400628677254","history_drop_reason":null,"meta_title":"Git - git-cherry-pick Documentation","meta_descriptions":[],"attrs_boilerpipe_text":"NAME\ngit-cherry-pick - Apply the changes introduced by some existing commits\nSYNOPSIS\ngit cherry-pick\n[--edit] [-n] [-m <parent-number>] [-s] [-x] [--ff]\n\t\t  [-S[<keyid>]]\n<commit>\n…\ngit cherry-pick\n(--continue | --skip | --abort | --quit)\nDESCRIPTION\nGiven one or more existing commits, apply the change each one\nintroduces, recording a new commit for each.  This requires your\nworking tree to be clean (no modifications from the HEAD commit).\nWhen it is not obvious how to apply a change, the following\nhappens:\nThe current branch and\nHEAD\npointer stay at the last commit\nsuccessfully made.\nThe\nCHERRY_PICK_HEAD\nref is set to point at the commit that\nintroduced the change that is difficult to apply.\nPaths in which the change applied cleanly are updated both\nin the index file and in your working tree.\nFor conflicting paths, the index file records up to three\nversions, as described in the \"TRUE MERGE\" section of\ngit-merge[1]\n.  The working tree files will include\na description of the conflict bracketed by the usual\nconflict markers\n<<<<<<<\nand\n>>>>>>>\n.\nNo other modifications are made.\nSee\ngit-merge[1]\nfor some hints on resolving such\nconflicts.\nOPTIONS\n<commit>\n…\nCommits to cherry-pick.\nFor a more complete list of ways to spell commits, see\ngitrevisions[7]\n.\nSets of commits can be passed but no traversal is done by\ndefault, as if the\n--no-walk\noption was specified, see\ngit-rev-list[1]\n. Note that specifying a range will\nfeed all\n<commit>\n… arguments to a single revision walk\n(see a later example that uses\nmaint master..next\n).\n-e\n--edit\nWith this option,\ngit cherry-pick\nwill let you edit the commit\nmessage prior to committing.\n--cleanup=<mode>\nThis option determines how the commit message will be cleaned up before\nbeing passed on to the commit machinery. See\ngit-commit[1]\nfor more\ndetails. In particular, if the\n<mode>\nis given a value of\nscissors\n,\nscissors will be appended to\nMERGE_MSG\nbefore being passed on in the case\nof a conflict.\n-x\nWhen recording the commit, append a line that says\n\"(cherry picked from commit …)\" to the original commit\nmessage in order to indicate which commit this change was\ncherry-picked from.  This is done only for cherry\npicks without conflicts.  Do not use this option if\nyou are cherry-picking from your private branch because\nthe information is useless to the recipient.  If on the\nother hand you are cherry-picking between two publicly\nvisible branches (e.g. backporting a fix to a\nmaintenance branch for an older release from a\ndevelopment branch), adding this information can be\nuseful.\n-r\nIt used to be that the command defaulted to do\n-x\ndescribed above, and\n-r\nwas to disable it.  Now the\ndefault is not to do\n-x\nso this option is a no-op.\n-m <parent-number>\n--mainline <parent-number>\nUsually you cannot cherry-pick a merge because you do not know which\nside of the merge should be considered the mainline.  This\noption specifies the parent number (starting from 1) of\nthe mainline and allows cherry-pick to replay the change\nrelative to the specified parent.\n-n\n--no-commit\nUsually the command automatically creates a sequence of commits.\nThis flag applies the changes necessary to cherry-pick\neach named commit to your working tree and the index,\nwithout making any commit.  In addition, when this\noption is used, your index does not have to match the\nHEAD commit.  The cherry-pick is done against the\nbeginning state of your index.\nThis is useful when cherry-picking more than one commits'\neffect to your index in a row.\n-s\n--signoff\nAdd a\nSigned-off-by\ntrailer at the end of the commit message.\nSee the signoff option in\ngit-commit[1]\nfor more information.\n-S[<keyid>]\n--gpg-sign[=<keyid>]\n--no-gpg-sign\nGPG-sign commits. The\nkeyid\nargument is optional and\ndefaults to the committer identity; if specified, it must be\nstuck to the option without a space.\n--no-gpg-sign\nis useful to\ncountermand both\ncommit.gpgSign\nconfiguration variable, and\nearlier\n--gpg-sign\n.\n--ff\nIf the current HEAD is the same as the parent of the\ncherry-pick’ed commit, then a fast forward to this commit will\nbe performed.\n--allow-empty\nBy default, cherry-picking an empty commit will fail,\nindicating that an explicit invocation of\ngit\ncommit\n--allow-empty\nis required. This option overrides that\nbehavior, allowing empty commits to be preserved automatically\nin a cherry-pick. Note that when \"--ff\" is in effect, empty\ncommits that meet the \"fast-forward\" requirement will be kept\neven without this option.  Note also, that use of this option only\nkeeps commits that were initially empty (i.e. the commit recorded the\nsame tree as its parent).  Commits which are made empty due to a\nprevious commit will cause the cherry-pick to fail.  To force the\ninclusion of those commits, use\n--empty=keep\n.\n--allow-empty-message\nBy default, cherry-picking a commit with an empty message will fail.\nThis option overrides that behavior, allowing commits with empty\nmessages to be cherry picked.\n--empty=(drop|keep|stop)\nHow to handle commits being cherry-picked that are redundant with\nchanges already in the current history.\ndrop\nThe commit will be dropped.\nkeep\nThe commit will be kept. Implies\n--allow-empty\n.\nstop\nThe cherry-pick will stop when the commit is applied, allowing\nyou to examine the commit. This is the default behavior.\nNote that\n--empty=drop\nand\n--empty=stop\nonly specify how to handle a\ncommit that was not initially empty, but rather became empty due to a previous\ncommit. Commits that were initially empty will still cause the cherry-pick to\nfail unless one of\n--empty=keep\nor\n--allow-empty\nare specified.\n--keep-redundant-commits\nDeprecated synonym for\n--empty=keep\n.\n--strategy=<strategy>\nUse the given merge strategy.  Should only be used once.\nSee the MERGE STRATEGIES section in\ngit-merge[1]\nfor details.\n-X<option>\n--strategy-option=<option>\nPass the merge strategy-specific option through to the\nmerge strategy.  See\ngit-merge[1]\nfor details.\n--rerere-autoupdate\n--no-rerere-autoupdate\nAfter the rerere mechanism reuses a recorded resolution on\nthe current conflict to update the files in the working\ntree, allow it to also update the index with the result of\nresolution.\n--no-rerere-autoupdate\nis a good way to\ndouble-check what\nrerere\ndid and catch potential\nmismerges, before committing the result to the index with a\nseparate\ngit\nadd\n.\nSEQUENCER SUBCOMMANDS\n--continue\nContinue the operation in progress using the information in\n.git\/sequencer\n.  Can be used to continue after resolving\nconflicts in a failed cherry-pick or revert.\n--skip\nSkip the current commit and continue with the rest of the\nsequence.\n--quit\nForget about the current operation in progress.  Can be used\nto clear the sequencer state after a failed cherry-pick or\nrevert.\n--abort\nCancel the operation and return to the pre-sequence state.\nEXAMPLES\ngit\ncherry-pick\nmaster\nApply the change introduced by the commit at the tip of the\nmaster branch and create a new commit with this change.\ngit\ncherry-pick\n..master\ngit\ncherry-pick\n^HEAD\nmaster\nApply the changes introduced by all commits that are ancestors\nof master but not of HEAD to produce new commits.\ngit\ncherry-pick\nmaint\nnext\n^master\ngit\ncherry-pick\nmaint\nmaster..next\nApply the changes introduced by all commits that are\nancestors of maint or next, but not master or any of its\nancestors.  Note that the latter does not mean\nmaint\nand\neverything between\nmaster\nand\nnext\n; specifically,\nmaint\nwill not be used if it is included in\nmaster\n.\ngit\ncherry-pick\nmaster~4\nmaster~2\nApply the changes introduced by the fifth and third last\ncommits pointed to by master and create 2 new commits with\nthese changes.\ngit\ncherry-pick\n-n\nmaster~1\nnext\nApply to the working tree and the index the changes introduced\nby the second last commit pointed to by master and by the last\ncommit pointed to by next, but do not create any commit with\nthese changes.\ngit\ncherry-pick\n--ff\n..next\nIf history is linear and HEAD is an ancestor of next, update\nthe working tree and advance the HEAD pointer to match next.\nOtherwise, apply the changes introduced by those commits that\nare in next but not HEAD to the current branch, creating a new\ncommit for each new change.\ngit\nrev-list\n--reverse\nmaster\n--\nREADME\n|\ngit\ncherry-pick\n-n\n--stdin\nApply the changes introduced by all commits on the master\nbranch that touched README to the working tree and index,\nso the result can be inspected and made into a single new\ncommit if suitable.\nThe following sequence attempts to backport a patch, bails out because\nthe code the patch applies to has changed too much, and then tries\nagain, this time exercising more care about matching up context lines.\n$ git cherry-pick topic^\n(1)\n$ git diff\n(2)\n$ git cherry-pick --abort\n(3)\n$ git cherry-pick -Xpatience topic^\n(4)\napply the change that would be shown by\ngit\nshow\ntopic^\n.\nIn this example, the patch does not apply cleanly, so\ninformation about the conflict is written to the index and\nworking tree and no new commit results.\nsummarize changes to be reconciled\ncancel the cherry-pick.  In other words, return to the\npre-cherry-pick state, preserving any local modifications\nyou had in the working tree.\ntry to apply the change introduced by\ntopic^\nagain,\nspending extra time to avoid mistakes based on incorrectly\nmatching context lines.","attrs_markdown":"[![Git](https:\/\/git-scm.com\/images\/logo@2x.png)](https:\/\/git-scm.com\/) \\--local-branching-on-the-cheap\n\n![](https:\/\/git-scm.com\/images\/dark-mode.svg)\n\n- [About](https:\/\/git-scm.com\/about)\n  - [Trademark](https:\/\/git-scm.com\/about\/trademark)\n- [Learn](https:\/\/git-scm.com\/learn)\n  - [Book](https:\/\/git-scm.com\/book)\n  - [Cheat Sheet](https:\/\/git-scm.com\/cheat-sheet)\n  - [Videos](https:\/\/git-scm.com\/videos)\n  - [External Links](https:\/\/git-scm.com\/doc\/ext)\n- [Tools](https:\/\/git-scm.com\/tools)\n  - [Command Line](https:\/\/git-scm.com\/tools\/command-line)\n  - [GUIs](https:\/\/git-scm.com\/tools\/guis)\n  - [Hosting](https:\/\/git-scm.com\/tools\/hosting)\n- [Reference](https:\/\/git-scm.com\/docs)\n- [Install](https:\/\/git-scm.com\/install\/linux)\n- [Community](https:\/\/git-scm.com\/community)\n\n- Table of Contents\n  - [NAME](https:\/\/git-scm.com\/docs\/git-cherry-pick#_name)\n  - [SYNOPSIS](https:\/\/git-scm.com\/docs\/git-cherry-pick#_synopsis)\n  - [DESCRIPTION](https:\/\/git-scm.com\/docs\/git-cherry-pick#_description)\n  - [OPTIONS](https:\/\/git-scm.com\/docs\/git-cherry-pick#_options)\n  - [SEQUENCER SUBCOMMANDS](https:\/\/git-scm.com\/docs\/git-cherry-pick#_sequencer_subcommands)\n  - [EXAMPLES](https:\/\/git-scm.com\/docs\/git-cherry-pick#_examples)\n  - [SEE ALSO](https:\/\/git-scm.com\/docs\/git-cherry-pick#_see_also)\n  - [GIT](https:\/\/git-scm.com\/docs\/git-cherry-pick#_git)\n\n[English ▾](https:\/\/git-scm.com\/docs\/git-cherry-pick)\n\nLocalized versions of **git-cherry-pick** manual\n\n1. [English](https:\/\/git-scm.com\/docs\/git-cherry-pick)\n2. [Français](https:\/\/git-scm.com\/docs\/git-cherry-pick\/fr)\n3. [Português (Brasil)](https:\/\/git-scm.com\/docs\/git-cherry-pick\/pt_BR)\n4. [Svenska](https:\/\/git-scm.com\/docs\/git-cherry-pick\/sv)\n5. [українська мова](https:\/\/git-scm.com\/docs\/git-cherry-pick\/uk)\n6. [简体中文](https:\/\/git-scm.com\/docs\/git-cherry-pick\/zh_HANS-CN)\n\nWant to read in your language or fix typos?  \n [You can help translate this page](https:\/\/github.com\/jnavila\/git-manpages-l10n).\n\n[Topics ▾](https:\/\/git-scm.com\/docs\/git-cherry-pick)\n\n### Setup and Config\n- [git](https:\/\/git-scm.com\/docs\/git)\n- [config](https:\/\/git-scm.com\/docs\/git-config)\n- [help](https:\/\/git-scm.com\/docs\/git-help)\n- [bugreport](https:\/\/git-scm.com\/docs\/git-bugreport)\n- [Credential helpers](https:\/\/git-scm.com\/doc\/credential-helpers)\n### Getting and Creating Projects\n- [init](https:\/\/git-scm.com\/docs\/git-init)\n- [clone](https:\/\/git-scm.com\/docs\/git-clone)\n### Basic Snapshotting\n- [add](https:\/\/git-scm.com\/docs\/git-add)\n- [status](https:\/\/git-scm.com\/docs\/git-status)\n- [diff](https:\/\/git-scm.com\/docs\/git-diff)\n- [commit](https:\/\/git-scm.com\/docs\/git-commit)\n- [notes](https:\/\/git-scm.com\/docs\/git-notes)\n- [restore](https:\/\/git-scm.com\/docs\/git-restore)\n- [reset](https:\/\/git-scm.com\/docs\/git-reset)\n- [rm](https:\/\/git-scm.com\/docs\/git-rm)\n- [mv](https:\/\/git-scm.com\/docs\/git-mv)\n### Branching and Merging\n- [branch](https:\/\/git-scm.com\/docs\/git-branch)\n- [checkout](https:\/\/git-scm.com\/docs\/git-checkout)\n- [switch](https:\/\/git-scm.com\/docs\/git-switch)\n- [merge](https:\/\/git-scm.com\/docs\/git-merge)\n- [mergetool](https:\/\/git-scm.com\/docs\/git-mergetool)\n- [log](https:\/\/git-scm.com\/docs\/git-log)\n- [stash](https:\/\/git-scm.com\/docs\/git-stash)\n- [tag](https:\/\/git-scm.com\/docs\/git-tag)\n- [worktree](https:\/\/git-scm.com\/docs\/git-worktree)\n### Sharing and Updating Projects\n- [fetch](https:\/\/git-scm.com\/docs\/git-fetch)\n- [pull](https:\/\/git-scm.com\/docs\/git-pull)\n- [push](https:\/\/git-scm.com\/docs\/git-push)\n- [remote](https:\/\/git-scm.com\/docs\/git-remote)\n- [submodule](https:\/\/git-scm.com\/docs\/git-submodule)\n\n### Inspection and Comparison\n- [show](https:\/\/git-scm.com\/docs\/git-show)\n- [log](https:\/\/git-scm.com\/docs\/git-log)\n- [diff](https:\/\/git-scm.com\/docs\/git-diff)\n- [difftool](https:\/\/git-scm.com\/docs\/git-difftool)\n- [range-diff](https:\/\/git-scm.com\/docs\/git-range-diff)\n- [shortlog](https:\/\/git-scm.com\/docs\/git-shortlog)\n- [describe](https:\/\/git-scm.com\/docs\/git-describe)\n### Patching\n- [apply](https:\/\/git-scm.com\/docs\/git-apply)\n- [cherry-pick](https:\/\/git-scm.com\/docs\/git-cherry-pick)\n- [diff](https:\/\/git-scm.com\/docs\/git-diff)\n- [rebase](https:\/\/git-scm.com\/docs\/git-rebase)\n- [revert](https:\/\/git-scm.com\/docs\/git-revert)\n### Debugging\n- [bisect](https:\/\/git-scm.com\/docs\/git-bisect)\n- [blame](https:\/\/git-scm.com\/docs\/git-blame)\n- [grep](https:\/\/git-scm.com\/docs\/git-grep)\n### Email\n- [am](https:\/\/git-scm.com\/docs\/git-am)\n- [apply](https:\/\/git-scm.com\/docs\/git-apply)\n- [imap-send](https:\/\/git-scm.com\/docs\/git-imap-send)\n- [format-patch](https:\/\/git-scm.com\/docs\/git-format-patch)\n- [send-email](https:\/\/git-scm.com\/docs\/git-send-email)\n- [request-pull](https:\/\/git-scm.com\/docs\/git-request-pull)\n### External Systems\n- [svn](https:\/\/git-scm.com\/docs\/git-svn)\n- [fast-import](https:\/\/git-scm.com\/docs\/git-fast-import)\n### Server Admin\n- [daemon](https:\/\/git-scm.com\/docs\/git-daemon)\n- [update-server-info](https:\/\/git-scm.com\/docs\/git-update-server-info)\n\n### Guides\n- [gitattributes](https:\/\/git-scm.com\/docs\/gitattributes)\n- [Command-line interface conventions](https:\/\/git-scm.com\/docs\/gitcli)\n- [Everyday Git](https:\/\/git-scm.com\/docs\/giteveryday)\n- [Frequently Asked Questions (FAQ)](https:\/\/git-scm.com\/docs\/gitfaq)\n- [Glossary](https:\/\/git-scm.com\/docs\/gitglossary)\n- [Hooks](https:\/\/git-scm.com\/docs\/githooks)\n- [gitignore](https:\/\/git-scm.com\/docs\/gitignore)\n- [gitmodules](https:\/\/git-scm.com\/docs\/gitmodules)\n- [Revisions](https:\/\/git-scm.com\/docs\/gitrevisions)\n- [Submodules](https:\/\/git-scm.com\/docs\/gitsubmodules)\n- [Tutorial](https:\/\/git-scm.com\/docs\/gittutorial)\n- [Workflows](https:\/\/git-scm.com\/docs\/gitworkflows)\n- [All guides...](https:\/\/git-scm.com\/docs\/git#_guides)\n### Administration\n- [clean](https:\/\/git-scm.com\/docs\/git-clean)\n- [gc](https:\/\/git-scm.com\/docs\/git-gc)\n- [fsck](https:\/\/git-scm.com\/docs\/git-fsck)\n- [reflog](https:\/\/git-scm.com\/docs\/git-reflog)\n- [filter-branch](https:\/\/git-scm.com\/docs\/git-filter-branch)\n- [instaweb](https:\/\/git-scm.com\/docs\/git-instaweb)\n- [archive](https:\/\/git-scm.com\/docs\/git-archive)\n- [bundle](https:\/\/git-scm.com\/docs\/git-bundle)\n### Plumbing Commands\n- [cat-file](https:\/\/git-scm.com\/docs\/git-cat-file)\n- [check-ignore](https:\/\/git-scm.com\/docs\/git-check-ignore)\n- [checkout-index](https:\/\/git-scm.com\/docs\/git-checkout-index)\n- [commit-tree](https:\/\/git-scm.com\/docs\/git-commit-tree)\n- [count-objects](https:\/\/git-scm.com\/docs\/git-count-objects)\n- [diff-index](https:\/\/git-scm.com\/docs\/git-diff-index)\n- [for-each-ref](https:\/\/git-scm.com\/docs\/git-for-each-ref)\n- [hash-object](https:\/\/git-scm.com\/docs\/git-hash-object)\n- [ls-files](https:\/\/git-scm.com\/docs\/git-ls-files)\n- [ls-tree](https:\/\/git-scm.com\/docs\/git-ls-tree)\n- [merge-base](https:\/\/git-scm.com\/docs\/git-merge-base)\n- [read-tree](https:\/\/git-scm.com\/docs\/git-read-tree)\n- [rev-list](https:\/\/git-scm.com\/docs\/git-rev-list)\n- [rev-parse](https:\/\/git-scm.com\/docs\/git-rev-parse)\n- [show-ref](https:\/\/git-scm.com\/docs\/git-show-ref)\n- [symbolic-ref](https:\/\/git-scm.com\/docs\/git-symbolic-ref)\n- [update-index](https:\/\/git-scm.com\/docs\/git-update-index)\n- [update-ref](https:\/\/git-scm.com\/docs\/git-update-ref)\n- [verify-pack](https:\/\/git-scm.com\/docs\/git-verify-pack)\n- [write-tree](https:\/\/git-scm.com\/docs\/git-write-tree)\n\n[Latest version ▾](https:\/\/git-scm.com\/docs\/git-cherry-pick)  git-cherry-pick last updated in 2.50.0\n\nChanges in the **git-cherry-pick** manual\n\n1. 2\\.50.1 → 2.53.0 no changes\n2. [2\\.50.0 ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) *2025-06-16*](https:\/\/git-scm.com\/docs\/git-cherry-pick\/2.50.0)\n3. 2\\.45.1 → 2.49.1 no changes\n4. [2\\.45.0 ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) *2024-04-29*](https:\/\/git-scm.com\/docs\/git-cherry-pick\/2.45.0)\n5. 2\\.39.4 → 2.44.4 no changes\n6. [2\\.39.3 ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) *2023-04-17*](https:\/\/git-scm.com\/docs\/git-cherry-pick\/2.39.3)\n7. 2\\.38.1 → 2.39.2 no changes\n8. [2\\.38.0 ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) *2022-10-02*](https:\/\/git-scm.com\/docs\/git-cherry-pick\/2.38.0)\n9. 2\\.35.1 → 2.37.7 no changes\n10. [2\\.35.0 ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) *2022-01-24*](https:\/\/git-scm.com\/docs\/git-cherry-pick\/2.35.0)\n11. 2\\.30.1 → 2.34.8 no changes\n12. [2\\.30.0 ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) *2020-12-27*](https:\/\/git-scm.com\/docs\/git-cherry-pick\/2.30.0)\n13. 2\\.27.1 → 2.29.3 no changes\n14. [2\\.27.0 ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) *2020-06-01*](https:\/\/git-scm.com\/docs\/git-cherry-pick\/2.27.0)\n15. 2\\.23.1 → 2.26.3 no changes\n16. [2\\.23.0 ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) *2019-08-16*](https:\/\/git-scm.com\/docs\/git-cherry-pick\/2.23.0)\n17. 2\\.22.1 → 2.22.5 no changes\n18. [2\\.22.0 ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) *2019-06-07*](https:\/\/git-scm.com\/docs\/git-cherry-pick\/2.22.0)\n19. 2\\.21.1 → 2.21.4 no changes\n20. [2\\.21.0 ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) *2019-02-24*](https:\/\/git-scm.com\/docs\/git-cherry-pick\/2.21.0)\n21. 2\\.10.5 → 2.20.5 no changes\n22. [2\\.9.5 ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) *2017-07-30*](https:\/\/git-scm.com\/docs\/git-cherry-pick\/2.9.5)\n23. 2\\.8.6 no changes\n24. [2\\.7.6 ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) *2017-07-30*](https:\/\/git-scm.com\/docs\/git-cherry-pick\/2.7.6)\n25. [2\\.6.7 ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) *2017-05-05*](https:\/\/git-scm.com\/docs\/git-cherry-pick\/2.6.7)\n26. 2\\.4.12 → 2.5.6 no changes\n27. [2\\.3.10 ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) *2015-09-28*](https:\/\/git-scm.com\/docs\/git-cherry-pick\/2.3.10)\n28. 2\\.1.4 → 2.2.3 no changes\n29. [2\\.0.5 ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/green-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/red-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) ![](https:\/\/git-scm.com\/images\/icons\/grey-dot.png) *2014-12-17*](https:\/\/git-scm.com\/docs\/git-cherry-pick\/2.0.5)\n\nCheck your version of git by running\n\n`git --version`\n\n## NAME\ngit-cherry-pick - Apply the changes introduced by some existing commits\n\n## SYNOPSIS\n```\ngit cherry-pick [--edit] [-n] [-m <parent-number>] [-s] [-x] [--ff]\n\t\t  [-S[<keyid>]] <commit>…\ngit cherry-pick (--continue | --skip | --abort | --quit)\n```\n\n## DESCRIPTION\nGiven one or more existing commits, apply the change each one introduces, recording a new commit for each. This requires your working tree to be clean (no modifications from the HEAD commit).\n\nWhen it is not obvious how to apply a change, the following happens:\n\n1. The current branch and `HEAD` pointer stay at the last commit successfully made.\n2. The `CHERRY_PICK_HEAD` ref is set to point at the commit that introduced the change that is difficult to apply.\n3. Paths in which the change applied cleanly are updated both in the index file and in your working tree.\n4. For conflicting paths, the index file records up to three versions, as described in the \"TRUE MERGE\" section of [git-merge\\[1\\]](https:\/\/git-scm.com\/docs\/git-merge). The working tree files will include a description of the conflict bracketed by the usual conflict markers *\\<\\<\\<\\<\\<\\<\\<* and *\\>\\>\\>\\>\\>\\>\\>*.\n5. No other modifications are made.\n\nSee [git-merge\\[1\\]](https:\/\/git-scm.com\/docs\/git-merge) for some hints on resolving such conflicts.\n\n## OPTIONS\n\\<commit\\>…\n\nCommits to cherry-pick. For a more complete list of ways to spell commits, see [gitrevisions\\[7\\]](https:\/\/git-scm.com\/docs\/gitrevisions). Sets of commits can be passed but no traversal is done by default, as if the `--no-walk` option was specified, see [git-rev-list\\[1\\]](https:\/\/git-scm.com\/docs\/git-rev-list). Note that specifying a range will feed all \\<commit\\>… arguments to a single revision walk (see a later example that uses *maint master..next*).\n\n\\-e\n\n\\--edit\n\nWith this option, *git cherry-pick* will let you edit the commit message prior to committing.\n\n\\--cleanup=\\<mode\\>\n\nThis option determines how the commit message will be cleaned up before being passed on to the commit machinery. See [git-commit\\[1\\]](https:\/\/git-scm.com\/docs\/git-commit) for more details. In particular, if the *\\<mode\\>* is given a value of `scissors`, scissors will be appended to `MERGE_MSG` before being passed on in the case of a conflict.\n\n\\-x\n\nWhen recording the commit, append a line that says \"(cherry picked from commit …)\" to the original commit message in order to indicate which commit this change was cherry-picked from. This is done only for cherry picks without conflicts. Do not use this option if you are cherry-picking from your private branch because the information is useless to the recipient. If on the other hand you are cherry-picking between two publicly visible branches (e.g. backporting a fix to a maintenance branch for an older release from a development branch), adding this information can be useful.\n\n\\-r\n\nIt used to be that the command defaulted to do `-x` described above, and `-r` was to disable it. Now the default is not to do `-x` so this option is a no-op.\n\n\\-m \\<parent-number\\>\n\n\\--mainline \\<parent-number\\>\n\nUsually you cannot cherry-pick a merge because you do not know which side of the merge should be considered the mainline. This option specifies the parent number (starting from 1) of the mainline and allows cherry-pick to replay the change relative to the specified parent.\n\n\\-n\n\n\\--no-commit\n\nUsually the command automatically creates a sequence of commits. This flag applies the changes necessary to cherry-pick each named commit to your working tree and the index, without making any commit. In addition, when this option is used, your index does not have to match the HEAD commit. The cherry-pick is done against the beginning state of your index.\n\nThis is useful when cherry-picking more than one commits' effect to your index in a row.\n\n\\-s\n\n\\--signoff\n\nAdd a `Signed-off-by` trailer at the end of the commit message. See the signoff option in [git-commit\\[1\\]](https:\/\/git-scm.com\/docs\/git-commit) for more information.\n\n\\-S\\[\\<keyid\\>\\]\n\n\\--gpg-sign\\[=\\<keyid\\>\\]\n\n\\--no-gpg-sign\n\nGPG-sign commits. The `keyid` argument is optional and defaults to the committer identity; if specified, it must be stuck to the option without a space. `--no-gpg-sign` is useful to countermand both `commit.gpgSign` configuration variable, and earlier `--gpg-sign`.\n\n\\--ff\n\nIf the current HEAD is the same as the parent of the cherry-pick’ed commit, then a fast forward to this commit will be performed.\n\n\\--allow-empty\n\nBy default, cherry-picking an empty commit will fail, indicating that an explicit invocation of `git` `commit` `--allow-empty` is required. This option overrides that behavior, allowing empty commits to be preserved automatically in a cherry-pick. Note that when \"--ff\" is in effect, empty commits that meet the \"fast-forward\" requirement will be kept even without this option. Note also, that use of this option only keeps commits that were initially empty (i.e. the commit recorded the same tree as its parent). Commits which are made empty due to a previous commit will cause the cherry-pick to fail. To force the inclusion of those commits, use `--empty=keep`.\n\n\\--allow-empty-message\n\nBy default, cherry-picking a commit with an empty message will fail. This option overrides that behavior, allowing commits with empty messages to be cherry picked.\n\n\\--empty=(drop\\|keep\\|stop)\n\nHow to handle commits being cherry-picked that are redundant with changes already in the current history.\n\n`drop`\n\nThe commit will be dropped.\n\n`keep`\n\nThe commit will be kept. Implies `--allow-empty`.\n\n`stop`\n\nThe cherry-pick will stop when the commit is applied, allowing you to examine the commit. This is the default behavior.\n\nNote that `--empty=drop` and `--empty=stop` only specify how to handle a commit that was not initially empty, but rather became empty due to a previous commit. Commits that were initially empty will still cause the cherry-pick to fail unless one of `--empty=keep` or `--allow-empty` are specified.\n\n\\--keep-redundant-commits\n\nDeprecated synonym for `--empty=keep`.\n\n\\--strategy=\\<strategy\\>\n\nUse the given merge strategy. Should only be used once. See the MERGE STRATEGIES section in [git-merge\\[1\\]](https:\/\/git-scm.com\/docs\/git-merge) for details.\n\n\\-X\\<option\\>\n\n\\--strategy-option=\\<option\\>\n\nPass the merge strategy-specific option through to the merge strategy. See [git-merge\\[1\\]](https:\/\/git-scm.com\/docs\/git-merge) for details.\n\n`--rerere-autoupdate`\n\n`--no-rerere-autoupdate`\n\nAfter the rerere mechanism reuses a recorded resolution on the current conflict to update the files in the working tree, allow it to also update the index with the result of resolution. `--no-rerere-autoupdate` is a good way to double-check what `rerere` did and catch potential mismerges, before committing the result to the index with a separate `git` `add`.\n\n## SEQUENCER SUBCOMMANDS\n\\--continue\n\nContinue the operation in progress using the information in `.git\/sequencer`. Can be used to continue after resolving conflicts in a failed cherry-pick or revert.\n\n\\--skip\n\nSkip the current commit and continue with the rest of the sequence.\n\n\\--quit\n\nForget about the current operation in progress. Can be used to clear the sequencer state after a failed cherry-pick or revert.\n\n\\--abort\n\nCancel the operation and return to the pre-sequence state.\n\n## EXAMPLES\n`git` `cherry-pick` `master`\n\nApply the change introduced by the commit at the tip of the master branch and create a new commit with this change.\n\n`git` `cherry-pick` `..master`\n\n`git` `cherry-pick` `^HEAD` `master`\n\nApply the changes introduced by all commits that are ancestors of master but not of HEAD to produce new commits.\n\n`git` `cherry-pick` `maint` `next` `^master`\n\n`git` `cherry-pick` `maint` `master..next`\n\nApply the changes introduced by all commits that are ancestors of maint or next, but not master or any of its ancestors. Note that the latter does not mean `maint` and everything between `master` and `next`; specifically, `maint` will not be used if it is included in `master`.\n\n`git` `cherry-pick` `master~4` `master~2`\n\nApply the changes introduced by the fifth and third last commits pointed to by master and create 2 new commits with these changes.\n\n`git` `cherry-pick` `-n` `master~1` `next`\n\nApply to the working tree and the index the changes introduced by the second last commit pointed to by master and by the last commit pointed to by next, but do not create any commit with these changes.\n\n`git` `cherry-pick` `--ff` `..next`\n\nIf history is linear and HEAD is an ancestor of next, update the working tree and advance the HEAD pointer to match next. Otherwise, apply the changes introduced by those commits that are in next but not HEAD to the current branch, creating a new commit for each new change.\n\n`git` `rev-list` `--reverse` `master` `--` `README` \\| `git` `cherry-pick` `-n` `--stdin`\n\nApply the changes introduced by all commits on the master branch that touched README to the working tree and index, so the result can be inspected and made into a single new commit if suitable.\n\nThe following sequence attempts to backport a patch, bails out because the code the patch applies to has changed too much, and then tries again, this time exercising more care about matching up context lines.\n```\n$ git cherry-pick topic^             (1)\n$ git diff                           (2)\n$ git cherry-pick --abort            (3)\n$ git cherry-pick -Xpatience topic^  (4)\n```\n1. apply the change that would be shown by `git` `show` `topic^`. In this example, the patch does not apply cleanly, so information about the conflict is written to the index and working tree and no new commit results.\n2. summarize changes to be reconciled\n3. cancel the cherry-pick. In other words, return to the pre-cherry-pick state, preserving any local modifications you had in the working tree.\n4. try to apply the change introduced by `topic^` again, spending extra time to avoid mistakes based on incorrectly matching context lines.\n\n## SEE ALSO\n[git-revert\\[1\\]](https:\/\/git-scm.com\/docs\/git-revert)\n\n## GIT\nPart of the [git\\[1\\]](https:\/\/git-scm.com\/docs\/git) suite\n### cherry-pick\n\n[About this site](https:\/\/git-scm.com\/site)  \n Patches, suggestions, and comments are welcome.\n\nGit is a member of [Software Freedom Conservancy](https:\/\/git-scm.com\/sfc)","attrs_readable_markdown":"## NAME\ngit-cherry-pick - Apply the changes introduced by some existing commits\n\n## SYNOPSIS\n```\ngit cherry-pick [--edit] [-n] [-m <parent-number>] [-s] [-x] [--ff]\n\t\t  [-S[<keyid>]] <commit>…\ngit cherry-pick (--continue | --skip | --abort | --quit)\n```\n\n## DESCRIPTION\nGiven one or more existing commits, apply the change each one introduces, recording a new commit for each. This requires your working tree to be clean (no modifications from the HEAD commit).\n\nWhen it is not obvious how to apply a change, the following happens:\n\n1. The current branch and `HEAD` pointer stay at the last commit successfully made.\n2. The `CHERRY_PICK_HEAD` ref is set to point at the commit that introduced the change that is difficult to apply.\n3. Paths in which the change applied cleanly are updated both in the index file and in your working tree.\n4. For conflicting paths, the index file records up to three versions, as described in the \"TRUE MERGE\" section of [git-merge\\[1\\]](https:\/\/git-scm.com\/docs\/git-merge). The working tree files will include a description of the conflict bracketed by the usual conflict markers *\\<\\<\\<\\<\\<\\<\\<* and *\\>\\>\\>\\>\\>\\>\\>*.\n5. No other modifications are made.\n\nSee [git-merge\\[1\\]](https:\/\/git-scm.com\/docs\/git-merge) for some hints on resolving such conflicts.\n\n## OPTIONS\n\\<commit\\>…\n\nCommits to cherry-pick. For a more complete list of ways to spell commits, see [gitrevisions\\[7\\]](https:\/\/git-scm.com\/docs\/gitrevisions). Sets of commits can be passed but no traversal is done by default, as if the `--no-walk` option was specified, see [git-rev-list\\[1\\]](https:\/\/git-scm.com\/docs\/git-rev-list). Note that specifying a range will feed all \\<commit\\>… arguments to a single revision walk (see a later example that uses *maint master..next*).\n\n\\-e\n\n\\--edit\n\nWith this option, *git cherry-pick* will let you edit the commit message prior to committing.\n\n\\--cleanup=\\<mode\\>\n\nThis option determines how the commit message will be cleaned up before being passed on to the commit machinery. See [git-commit\\[1\\]](https:\/\/git-scm.com\/docs\/git-commit) for more details. In particular, if the *\\<mode\\>* is given a value of `scissors`, scissors will be appended to `MERGE_MSG` before being passed on in the case of a conflict.\n\n\\-x\n\nWhen recording the commit, append a line that says \"(cherry picked from commit …)\" to the original commit message in order to indicate which commit this change was cherry-picked from. This is done only for cherry picks without conflicts. Do not use this option if you are cherry-picking from your private branch because the information is useless to the recipient. If on the other hand you are cherry-picking between two publicly visible branches (e.g. backporting a fix to a maintenance branch for an older release from a development branch), adding this information can be useful.\n\n\\-r\n\nIt used to be that the command defaulted to do `-x` described above, and `-r` was to disable it. Now the default is not to do `-x` so this option is a no-op.\n\n\\-m \\<parent-number\\>\n\n\\--mainline \\<parent-number\\>\n\nUsually you cannot cherry-pick a merge because you do not know which side of the merge should be considered the mainline. This option specifies the parent number (starting from 1) of the mainline and allows cherry-pick to replay the change relative to the specified parent.\n\n\\-n\n\n\\--no-commit\n\nUsually the command automatically creates a sequence of commits. This flag applies the changes necessary to cherry-pick each named commit to your working tree and the index, without making any commit. In addition, when this option is used, your index does not have to match the HEAD commit. The cherry-pick is done against the beginning state of your index.\n\nThis is useful when cherry-picking more than one commits' effect to your index in a row.\n\n\\-s\n\n\\--signoff\n\nAdd a `Signed-off-by` trailer at the end of the commit message. See the signoff option in [git-commit\\[1\\]](https:\/\/git-scm.com\/docs\/git-commit) for more information.\n\n\\-S\\[\\<keyid\\>\\]\n\n\\--gpg-sign\\[=\\<keyid\\>\\]\n\n\\--no-gpg-sign\n\nGPG-sign commits. The `keyid` argument is optional and defaults to the committer identity; if specified, it must be stuck to the option without a space. `--no-gpg-sign` is useful to countermand both `commit.gpgSign` configuration variable, and earlier `--gpg-sign`.\n\n\\--ff\n\nIf the current HEAD is the same as the parent of the cherry-pick’ed commit, then a fast forward to this commit will be performed.\n\n\\--allow-empty\n\nBy default, cherry-picking an empty commit will fail, indicating that an explicit invocation of `git` `commit` `--allow-empty` is required. This option overrides that behavior, allowing empty commits to be preserved automatically in a cherry-pick. Note that when \"--ff\" is in effect, empty commits that meet the \"fast-forward\" requirement will be kept even without this option. Note also, that use of this option only keeps commits that were initially empty (i.e. the commit recorded the same tree as its parent). Commits which are made empty due to a previous commit will cause the cherry-pick to fail. To force the inclusion of those commits, use `--empty=keep`.\n\n\\--allow-empty-message\n\nBy default, cherry-picking a commit with an empty message will fail. This option overrides that behavior, allowing commits with empty messages to be cherry picked.\n\n\\--empty=(drop\\|keep\\|stop)\n\nHow to handle commits being cherry-picked that are redundant with changes already in the current history.\n\n`drop`\n\nThe commit will be dropped.\n\n`keep`\n\nThe commit will be kept. Implies `--allow-empty`.\n\n`stop`\n\nThe cherry-pick will stop when the commit is applied, allowing you to examine the commit. This is the default behavior.\n\nNote that `--empty=drop` and `--empty=stop` only specify how to handle a commit that was not initially empty, but rather became empty due to a previous commit. Commits that were initially empty will still cause the cherry-pick to fail unless one of `--empty=keep` or `--allow-empty` are specified.\n\n\\--keep-redundant-commits\n\nDeprecated synonym for `--empty=keep`.\n\n\\--strategy=\\<strategy\\>\n\nUse the given merge strategy. Should only be used once. See the MERGE STRATEGIES section in [git-merge\\[1\\]](https:\/\/git-scm.com\/docs\/git-merge) for details.\n\n\\-X\\<option\\>\n\n\\--strategy-option=\\<option\\>\n\nPass the merge strategy-specific option through to the merge strategy. See [git-merge\\[1\\]](https:\/\/git-scm.com\/docs\/git-merge) for details.\n\n`--rerere-autoupdate`\n\n`--no-rerere-autoupdate`\n\nAfter the rerere mechanism reuses a recorded resolution on the current conflict to update the files in the working tree, allow it to also update the index with the result of resolution. `--no-rerere-autoupdate` is a good way to double-check what `rerere` did and catch potential mismerges, before committing the result to the index with a separate `git` `add`.\n\n## SEQUENCER SUBCOMMANDS\n\\--continue\n\nContinue the operation in progress using the information in `.git\/sequencer`. Can be used to continue after resolving conflicts in a failed cherry-pick or revert.\n\n\\--skip\n\nSkip the current commit and continue with the rest of the sequence.\n\n\\--quit\n\nForget about the current operation in progress. Can be used to clear the sequencer state after a failed cherry-pick or revert.\n\n\\--abort\n\nCancel the operation and return to the pre-sequence state.\n\n## EXAMPLES\n`git` `cherry-pick` `master`\n\nApply the change introduced by the commit at the tip of the master branch and create a new commit with this change.\n\n`git` `cherry-pick` `..master`\n\n`git` `cherry-pick` `^HEAD` `master`\n\nApply the changes introduced by all commits that are ancestors of master but not of HEAD to produce new commits.\n\n`git` `cherry-pick` `maint` `next` `^master`\n\n`git` `cherry-pick` `maint` `master..next`\n\nApply the changes introduced by all commits that are ancestors of maint or next, but not master or any of its ancestors. Note that the latter does not mean `maint` and everything between `master` and `next`; specifically, `maint` will not be used if it is included in `master`.\n\n`git` `cherry-pick` `master~4` `master~2`\n\nApply the changes introduced by the fifth and third last commits pointed to by master and create 2 new commits with these changes.\n\n`git` `cherry-pick` `-n` `master~1` `next`\n\nApply to the working tree and the index the changes introduced by the second last commit pointed to by master and by the last commit pointed to by next, but do not create any commit with these changes.\n\n`git` `cherry-pick` `--ff` `..next`\n\nIf history is linear and HEAD is an ancestor of next, update the working tree and advance the HEAD pointer to match next. Otherwise, apply the changes introduced by those commits that are in next but not HEAD to the current branch, creating a new commit for each new change.\n\n`git` `rev-list` `--reverse` `master` `--` `README` \\| `git` `cherry-pick` `-n` `--stdin`\n\nApply the changes introduced by all commits on the master branch that touched README to the working tree and index, so the result can be inspected and made into a single new commit if suitable.\n\nThe following sequence attempts to backport a patch, bails out because the code the patch applies to has changed too much, and then tries again, this time exercising more care about matching up context lines.\n```\n$ git cherry-pick topic^             (1)\n$ git diff                           (2)\n$ git cherry-pick --abort            (3)\n$ git cherry-pick -Xpatience topic^  (4)\n```\n1. apply the change that would be shown by `git` `show` `topic^`. In this example, the patch does not apply cleanly, so information about the conflict is written to the index and working tree and no new commit results.\n2. summarize changes to be reconciled\n3. cancel the cherry-pick. In other words, return to the pre-cherry-pick state, preserving any local modifications you had in the working tree.\n4. try to apply the change introduced by `topic^` again, spending extra time to avoid mistakes based on incorrectly matching context lines.","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 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://git-scm.com/docs/git-cherry-pick
Last Crawled	2026-04-10 23:15:38 (8 hours ago)
First Indexed	2013-08-09 02:06:07 (12 years ago)
HTTP Status Code	200
Meta Title	Git - git-cherry-pick Documentation
Meta Description	null
Meta Canonical	null
Boilerpipe Text	NAME git-cherry-pick - Apply the changes introduced by some existing commits SYNOPSIS git cherry-pick [--edit] [-n] [-m <parent-number>] [-s] [-x] [--ff] [-S[<keyid>]] <commit> … git cherry-pick (--continue \| --skip \| --abort \| --quit) DESCRIPTION Given one or more existing commits, apply the change each one introduces, recording a new commit for each. This requires your working tree to be clean (no modifications from the HEAD commit). When it is not obvious how to apply a change, the following happens: The current branch and HEAD pointer stay at the last commit successfully made. The CHERRY_PICK_HEAD ref is set to point at the commit that introduced the change that is difficult to apply. Paths in which the change applied cleanly are updated both in the index file and in your working tree. For conflicting paths, the index file records up to three versions, as described in the "TRUE MERGE" section of git-merge[1] . The working tree files will include a description of the conflict bracketed by the usual conflict markers <<<<<<< and >>>>>>> . No other modifications are made. See git-merge[1] for some hints on resolving such conflicts. OPTIONS <commit> … Commits to cherry-pick. For a more complete list of ways to spell commits, see gitrevisions[7] . Sets of commits can be passed but no traversal is done by default, as if the --no-walk option was specified, see git-rev-list[1] . Note that specifying a range will feed all <commit> … arguments to a single revision walk (see a later example that uses maint master..next ). -e --edit With this option, git cherry-pick will let you edit the commit message prior to committing. --cleanup=<mode> This option determines how the commit message will be cleaned up before being passed on to the commit machinery. See git-commit[1] for more details. In particular, if the <mode> is given a value of scissors , scissors will be appended to MERGE_MSG before being passed on in the case of a conflict. -x When recording the commit, append a line that says "(cherry picked from commit …)" to the original commit message in order to indicate which commit this change was cherry-picked from. This is done only for cherry picks without conflicts. Do not use this option if you are cherry-picking from your private branch because the information is useless to the recipient. If on the other hand you are cherry-picking between two publicly visible branches (e.g. backporting a fix to a maintenance branch for an older release from a development branch), adding this information can be useful. -r It used to be that the command defaulted to do -x described above, and -r was to disable it. Now the default is not to do -x so this option is a no-op. -m <parent-number> --mainline <parent-number> Usually you cannot cherry-pick a merge because you do not know which side of the merge should be considered the mainline. This option specifies the parent number (starting from 1) of the mainline and allows cherry-pick to replay the change relative to the specified parent. -n --no-commit Usually the command automatically creates a sequence of commits. This flag applies the changes necessary to cherry-pick each named commit to your working tree and the index, without making any commit. In addition, when this option is used, your index does not have to match the HEAD commit. The cherry-pick is done against the beginning state of your index. This is useful when cherry-picking more than one commits' effect to your index in a row. -s --signoff Add a Signed-off-by trailer at the end of the commit message. See the signoff option in git-commit[1] for more information. -S[<keyid>] --gpg-sign[=<keyid>] --no-gpg-sign GPG-sign commits. The keyid argument is optional and defaults to the committer identity; if specified, it must be stuck to the option without a space. --no-gpg-sign is useful to countermand both commit.gpgSign configuration variable, and earlier --gpg-sign . --ff If the current HEAD is the same as the parent of the cherry-pick’ed commit, then a fast forward to this commit will be performed. --allow-empty By default, cherry-picking an empty commit will fail, indicating that an explicit invocation of git commit --allow-empty is required. This option overrides that behavior, allowing empty commits to be preserved automatically in a cherry-pick. Note that when "--ff" is in effect, empty commits that meet the "fast-forward" requirement will be kept even without this option. Note also, that use of this option only keeps commits that were initially empty (i.e. the commit recorded the same tree as its parent). Commits which are made empty due to a previous commit will cause the cherry-pick to fail. To force the inclusion of those commits, use --empty=keep . --allow-empty-message By default, cherry-picking a commit with an empty message will fail. This option overrides that behavior, allowing commits with empty messages to be cherry picked. --empty=(drop\|keep\|stop) How to handle commits being cherry-picked that are redundant with changes already in the current history. drop The commit will be dropped. keep The commit will be kept. Implies --allow-empty . stop The cherry-pick will stop when the commit is applied, allowing you to examine the commit. This is the default behavior. Note that --empty=drop and --empty=stop only specify how to handle a commit that was not initially empty, but rather became empty due to a previous commit. Commits that were initially empty will still cause the cherry-pick to fail unless one of --empty=keep or --allow-empty are specified. --keep-redundant-commits Deprecated synonym for --empty=keep . --strategy=<strategy> Use the given merge strategy. Should only be used once. See the MERGE STRATEGIES section in git-merge[1] for details. -X<option> --strategy-option=<option> Pass the merge strategy-specific option through to the merge strategy. See git-merge[1] for details. --rerere-autoupdate --no-rerere-autoupdate After the rerere mechanism reuses a recorded resolution on the current conflict to update the files in the working tree, allow it to also update the index with the result of resolution. --no-rerere-autoupdate is a good way to double-check what rerere did and catch potential mismerges, before committing the result to the index with a separate git add . SEQUENCER SUBCOMMANDS --continue Continue the operation in progress using the information in .git/sequencer . Can be used to continue after resolving conflicts in a failed cherry-pick or revert. --skip Skip the current commit and continue with the rest of the sequence. --quit Forget about the current operation in progress. Can be used to clear the sequencer state after a failed cherry-pick or revert. --abort Cancel the operation and return to the pre-sequence state. EXAMPLES git cherry-pick master Apply the change introduced by the commit at the tip of the master branch and create a new commit with this change. git cherry-pick ..master git cherry-pick ^HEAD master Apply the changes introduced by all commits that are ancestors of master but not of HEAD to produce new commits. git cherry-pick maint next ^master git cherry-pick maint master..next Apply the changes introduced by all commits that are ancestors of maint or next, but not master or any of its ancestors. Note that the latter does not mean maint and everything between master and next ; specifically, maint will not be used if it is included in master . git cherry-pick master~4 master~2 Apply the changes introduced by the fifth and third last commits pointed to by master and create 2 new commits with these changes. git cherry-pick -n master~1 next Apply to the working tree and the index the changes introduced by the second last commit pointed to by master and by the last commit pointed to by next, but do not create any commit with these changes. git cherry-pick --ff ..next If history is linear and HEAD is an ancestor of next, update the working tree and advance the HEAD pointer to match next. Otherwise, apply the changes introduced by those commits that are in next but not HEAD to the current branch, creating a new commit for each new change. git rev-list --reverse master -- README \| git cherry-pick -n --stdin Apply the changes introduced by all commits on the master branch that touched README to the working tree and index, so the result can be inspected and made into a single new commit if suitable. The following sequence attempts to backport a patch, bails out because the code the patch applies to has changed too much, and then tries again, this time exercising more care about matching up context lines. $ git cherry-pick topic^ (1) $ git diff (2) $ git cherry-pick --abort (3) $ git cherry-pick -Xpatience topic^ (4) apply the change that would be shown by git show topic^ . In this example, the patch does not apply cleanly, so information about the conflict is written to the index and working tree and no new commit results. summarize changes to be reconciled cancel the cherry-pick. In other words, return to the pre-cherry-pick state, preserving any local modifications you had in the working tree. try to apply the change introduced by topic^ again, spending extra time to avoid mistakes based on incorrectly matching context lines.
Markdown	[![Git](https://git-scm.com/images/logo@2x.png)](https://git-scm.com/) \--local-branching-on-the-cheap ![](https://git-scm.com/images/dark-mode.svg) - [About](https://git-scm.com/about) - [Trademark](https://git-scm.com/about/trademark) - [Learn](https://git-scm.com/learn) - [Book](https://git-scm.com/book) - [Cheat Sheet](https://git-scm.com/cheat-sheet) - [Videos](https://git-scm.com/videos) - [External Links](https://git-scm.com/doc/ext) - [Tools](https://git-scm.com/tools) - [Command Line](https://git-scm.com/tools/command-line) - [GUIs](https://git-scm.com/tools/guis) - [Hosting](https://git-scm.com/tools/hosting) - [Reference](https://git-scm.com/docs) - [Install](https://git-scm.com/install/linux) - [Community](https://git-scm.com/community) - Table of Contents - [NAME](https://git-scm.com/docs/git-cherry-pick#_name) - [SYNOPSIS](https://git-scm.com/docs/git-cherry-pick#_synopsis) - [DESCRIPTION](https://git-scm.com/docs/git-cherry-pick#_description) - [OPTIONS](https://git-scm.com/docs/git-cherry-pick#_options) - [SEQUENCER SUBCOMMANDS](https://git-scm.com/docs/git-cherry-pick#_sequencer_subcommands) - [EXAMPLES](https://git-scm.com/docs/git-cherry-pick#_examples) - [SEE ALSO](https://git-scm.com/docs/git-cherry-pick#_see_also) - [GIT](https://git-scm.com/docs/git-cherry-pick#_git) [English ▾](https://git-scm.com/docs/git-cherry-pick) Localized versions of git-cherry-pick manual 1. [English](https://git-scm.com/docs/git-cherry-pick) 2. [Français](https://git-scm.com/docs/git-cherry-pick/fr) 3. [Português (Brasil)](https://git-scm.com/docs/git-cherry-pick/pt_BR) 4. [Svenska](https://git-scm.com/docs/git-cherry-pick/sv) 5. [українська мова](https://git-scm.com/docs/git-cherry-pick/uk) 6. [简体中文](https://git-scm.com/docs/git-cherry-pick/zh_HANS-CN) Want to read in your language or fix typos? [You can help translate this page](https://github.com/jnavila/git-manpages-l10n). [Topics ▾](https://git-scm.com/docs/git-cherry-pick) ### Setup and Config - [git](https://git-scm.com/docs/git) - [config](https://git-scm.com/docs/git-config) - [help](https://git-scm.com/docs/git-help) - [bugreport](https://git-scm.com/docs/git-bugreport) - [Credential helpers](https://git-scm.com/doc/credential-helpers) ### Getting and Creating Projects - [init](https://git-scm.com/docs/git-init) - [clone](https://git-scm.com/docs/git-clone) ### Basic Snapshotting - [add](https://git-scm.com/docs/git-add) - [status](https://git-scm.com/docs/git-status) - [diff](https://git-scm.com/docs/git-diff) - [commit](https://git-scm.com/docs/git-commit) - [notes](https://git-scm.com/docs/git-notes) - [restore](https://git-scm.com/docs/git-restore) - [reset](https://git-scm.com/docs/git-reset) - [rm](https://git-scm.com/docs/git-rm) - [mv](https://git-scm.com/docs/git-mv) ### Branching and Merging - [branch](https://git-scm.com/docs/git-branch) - [checkout](https://git-scm.com/docs/git-checkout) - [switch](https://git-scm.com/docs/git-switch) - [merge](https://git-scm.com/docs/git-merge) - [mergetool](https://git-scm.com/docs/git-mergetool) - [log](https://git-scm.com/docs/git-log) - [stash](https://git-scm.com/docs/git-stash) - [tag](https://git-scm.com/docs/git-tag) - [worktree](https://git-scm.com/docs/git-worktree) ### Sharing and Updating Projects - [fetch](https://git-scm.com/docs/git-fetch) - [pull](https://git-scm.com/docs/git-pull) - [push](https://git-scm.com/docs/git-push) - [remote](https://git-scm.com/docs/git-remote) - [submodule](https://git-scm.com/docs/git-submodule) ### Inspection and Comparison - [show](https://git-scm.com/docs/git-show) - [log](https://git-scm.com/docs/git-log) - [diff](https://git-scm.com/docs/git-diff) - [difftool](https://git-scm.com/docs/git-difftool) - [range-diff](https://git-scm.com/docs/git-range-diff) - [shortlog](https://git-scm.com/docs/git-shortlog) - [describe](https://git-scm.com/docs/git-describe) ### Patching - [apply](https://git-scm.com/docs/git-apply) - [cherry-pick](https://git-scm.com/docs/git-cherry-pick) - [diff](https://git-scm.com/docs/git-diff) - [rebase](https://git-scm.com/docs/git-rebase) - [revert](https://git-scm.com/docs/git-revert) ### Debugging - [bisect](https://git-scm.com/docs/git-bisect) - [blame](https://git-scm.com/docs/git-blame) - [grep](https://git-scm.com/docs/git-grep) ### Email - [am](https://git-scm.com/docs/git-am) - [apply](https://git-scm.com/docs/git-apply) - [imap-send](https://git-scm.com/docs/git-imap-send) - [format-patch](https://git-scm.com/docs/git-format-patch) - [send-email](https://git-scm.com/docs/git-send-email) - [request-pull](https://git-scm.com/docs/git-request-pull) ### External Systems - [svn](https://git-scm.com/docs/git-svn) - [fast-import](https://git-scm.com/docs/git-fast-import) ### Server Admin - [daemon](https://git-scm.com/docs/git-daemon) - [update-server-info](https://git-scm.com/docs/git-update-server-info) ### Guides - [gitattributes](https://git-scm.com/docs/gitattributes) - [Command-line interface conventions](https://git-scm.com/docs/gitcli) - [Everyday Git](https://git-scm.com/docs/giteveryday) - [Frequently Asked Questions (FAQ)](https://git-scm.com/docs/gitfaq) - [Glossary](https://git-scm.com/docs/gitglossary) - [Hooks](https://git-scm.com/docs/githooks) - [gitignore](https://git-scm.com/docs/gitignore) - [gitmodules](https://git-scm.com/docs/gitmodules) - [Revisions](https://git-scm.com/docs/gitrevisions) - [Submodules](https://git-scm.com/docs/gitsubmodules) - [Tutorial](https://git-scm.com/docs/gittutorial) - [Workflows](https://git-scm.com/docs/gitworkflows) - [All guides...](https://git-scm.com/docs/git#_guides) ### Administration - [clean](https://git-scm.com/docs/git-clean) - [gc](https://git-scm.com/docs/git-gc) - [fsck](https://git-scm.com/docs/git-fsck) - [reflog](https://git-scm.com/docs/git-reflog) - [filter-branch](https://git-scm.com/docs/git-filter-branch) - [instaweb](https://git-scm.com/docs/git-instaweb) - [archive](https://git-scm.com/docs/git-archive) - [bundle](https://git-scm.com/docs/git-bundle) ### Plumbing Commands - [cat-file](https://git-scm.com/docs/git-cat-file) - [check-ignore](https://git-scm.com/docs/git-check-ignore) - [checkout-index](https://git-scm.com/docs/git-checkout-index) - [commit-tree](https://git-scm.com/docs/git-commit-tree) - [count-objects](https://git-scm.com/docs/git-count-objects) - [diff-index](https://git-scm.com/docs/git-diff-index) - [for-each-ref](https://git-scm.com/docs/git-for-each-ref) - [hash-object](https://git-scm.com/docs/git-hash-object) - [ls-files](https://git-scm.com/docs/git-ls-files) - [ls-tree](https://git-scm.com/docs/git-ls-tree) - [merge-base](https://git-scm.com/docs/git-merge-base) - [read-tree](https://git-scm.com/docs/git-read-tree) - [rev-list](https://git-scm.com/docs/git-rev-list) - [rev-parse](https://git-scm.com/docs/git-rev-parse) - [show-ref](https://git-scm.com/docs/git-show-ref) - [symbolic-ref](https://git-scm.com/docs/git-symbolic-ref) - [update-index](https://git-scm.com/docs/git-update-index) - [update-ref](https://git-scm.com/docs/git-update-ref) - [verify-pack](https://git-scm.com/docs/git-verify-pack) - [write-tree](https://git-scm.com/docs/git-write-tree) [Latest version ▾](https://git-scm.com/docs/git-cherry-pick) git-cherry-pick last updated in 2.50.0 Changes in the git-cherry-pick manual 1. 2\.50.1 → 2.53.0 no changes 2. [2\.50.0 ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) 2025-06-16](https://git-scm.com/docs/git-cherry-pick/2.50.0) 3. 2\.45.1 → 2.49.1 no changes 4. [2\.45.0 ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) 2024-04-29](https://git-scm.com/docs/git-cherry-pick/2.45.0) 5. 2\.39.4 → 2.44.4 no changes 6. [2\.39.3 ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) 2023-04-17](https://git-scm.com/docs/git-cherry-pick/2.39.3) 7. 2\.38.1 → 2.39.2 no changes 8. [2\.38.0 ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) 2022-10-02](https://git-scm.com/docs/git-cherry-pick/2.38.0) 9. 2\.35.1 → 2.37.7 no changes 10. [2\.35.0 ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) 2022-01-24](https://git-scm.com/docs/git-cherry-pick/2.35.0) 11. 2\.30.1 → 2.34.8 no changes 12. [2\.30.0 ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) 2020-12-27](https://git-scm.com/docs/git-cherry-pick/2.30.0) 13. 2\.27.1 → 2.29.3 no changes 14. [2\.27.0 ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) 2020-06-01](https://git-scm.com/docs/git-cherry-pick/2.27.0) 15. 2\.23.1 → 2.26.3 no changes 16. [2\.23.0 ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) 2019-08-16](https://git-scm.com/docs/git-cherry-pick/2.23.0) 17. 2\.22.1 → 2.22.5 no changes 18. [2\.22.0 ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) 2019-06-07](https://git-scm.com/docs/git-cherry-pick/2.22.0) 19. 2\.21.1 → 2.21.4 no changes 20. [2\.21.0 ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) 2019-02-24](https://git-scm.com/docs/git-cherry-pick/2.21.0) 21. 2\.10.5 → 2.20.5 no changes 22. [2\.9.5 ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) 2017-07-30](https://git-scm.com/docs/git-cherry-pick/2.9.5) 23. 2\.8.6 no changes 24. [2\.7.6 ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) 2017-07-30](https://git-scm.com/docs/git-cherry-pick/2.7.6) 25. [2\.6.7 ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) 2017-05-05](https://git-scm.com/docs/git-cherry-pick/2.6.7) 26. 2\.4.12 → 2.5.6 no changes 27. [2\.3.10 ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) 2015-09-28](https://git-scm.com/docs/git-cherry-pick/2.3.10) 28. 2\.1.4 → 2.2.3 no changes 29. [2\.0.5 ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/green-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/red-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) ![](https://git-scm.com/images/icons/grey-dot.png) 2014-12-17](https://git-scm.com/docs/git-cherry-pick/2.0.5) Check your version of git by running `git --version` ## NAME git-cherry-pick - Apply the changes introduced by some existing commits ## SYNOPSIS ``` git cherry-pick [--edit] [-n] [-m <parent-number>] [-s] [-x] [--ff] [-S[<keyid>]] <commit>… git cherry-pick (--continue \| --skip \| --abort \| --quit) ``` ## DESCRIPTION Given one or more existing commits, apply the change each one introduces, recording a new commit for each. This requires your working tree to be clean (no modifications from the HEAD commit). When it is not obvious how to apply a change, the following happens: 1. The current branch and `HEAD` pointer stay at the last commit successfully made. 2. The `CHERRY_PICK_HEAD` ref is set to point at the commit that introduced the change that is difficult to apply. 3. Paths in which the change applied cleanly are updated both in the index file and in your working tree. 4. For conflicting paths, the index file records up to three versions, as described in the "TRUE MERGE" section of [git-merge\[1\]](https://git-scm.com/docs/git-merge). The working tree files will include a description of the conflict bracketed by the usual conflict markers \<\<\<\<\<\<\< and \>\>\>\>\>\>\>. 5. No other modifications are made. See [git-merge\[1\]](https://git-scm.com/docs/git-merge) for some hints on resolving such conflicts. ## OPTIONS \<commit\>… Commits to cherry-pick. For a more complete list of ways to spell commits, see [gitrevisions\[7\]](https://git-scm.com/docs/gitrevisions). Sets of commits can be passed but no traversal is done by default, as if the `--no-walk` option was specified, see [git-rev-list\[1\]](https://git-scm.com/docs/git-rev-list). Note that specifying a range will feed all \<commit\>… arguments to a single revision walk (see a later example that uses maint master..next). \-e \--edit With this option, git cherry-pick will let you edit the commit message prior to committing. \--cleanup=\<mode\> This option determines how the commit message will be cleaned up before being passed on to the commit machinery. See [git-commit\[1\]](https://git-scm.com/docs/git-commit) for more details. In particular, if the \<mode\> is given a value of `scissors`, scissors will be appended to `MERGE_MSG` before being passed on in the case of a conflict. \-x When recording the commit, append a line that says "(cherry picked from commit …)" to the original commit message in order to indicate which commit this change was cherry-picked from. This is done only for cherry picks without conflicts. Do not use this option if you are cherry-picking from your private branch because the information is useless to the recipient. If on the other hand you are cherry-picking between two publicly visible branches (e.g. backporting a fix to a maintenance branch for an older release from a development branch), adding this information can be useful. \-r It used to be that the command defaulted to do `-x` described above, and `-r` was to disable it. Now the default is not to do `-x` so this option is a no-op. \-m \<parent-number\> \--mainline \<parent-number\> Usually you cannot cherry-pick a merge because you do not know which side of the merge should be considered the mainline. This option specifies the parent number (starting from 1) of the mainline and allows cherry-pick to replay the change relative to the specified parent. \-n \--no-commit Usually the command automatically creates a sequence of commits. This flag applies the changes necessary to cherry-pick each named commit to your working tree and the index, without making any commit. In addition, when this option is used, your index does not have to match the HEAD commit. The cherry-pick is done against the beginning state of your index. This is useful when cherry-picking more than one commits' effect to your index in a row. \-s \--signoff Add a `Signed-off-by` trailer at the end of the commit message. See the signoff option in [git-commit\[1\]](https://git-scm.com/docs/git-commit) for more information. \-S\[\<keyid\>\] \--gpg-sign\[=\<keyid\>\] \--no-gpg-sign GPG-sign commits. The `keyid` argument is optional and defaults to the committer identity; if specified, it must be stuck to the option without a space. `--no-gpg-sign` is useful to countermand both `commit.gpgSign` configuration variable, and earlier `--gpg-sign`. \--ff If the current HEAD is the same as the parent of the cherry-pick’ed commit, then a fast forward to this commit will be performed. \--allow-empty By default, cherry-picking an empty commit will fail, indicating that an explicit invocation of `git` `commit` `--allow-empty` is required. This option overrides that behavior, allowing empty commits to be preserved automatically in a cherry-pick. Note that when "--ff" is in effect, empty commits that meet the "fast-forward" requirement will be kept even without this option. Note also, that use of this option only keeps commits that were initially empty (i.e. the commit recorded the same tree as its parent). Commits which are made empty due to a previous commit will cause the cherry-pick to fail. To force the inclusion of those commits, use `--empty=keep`. \--allow-empty-message By default, cherry-picking a commit with an empty message will fail. This option overrides that behavior, allowing commits with empty messages to be cherry picked. \--empty=(drop\\|keep\\|stop) How to handle commits being cherry-picked that are redundant with changes already in the current history. `drop` The commit will be dropped. `keep` The commit will be kept. Implies `--allow-empty`. `stop` The cherry-pick will stop when the commit is applied, allowing you to examine the commit. This is the default behavior. Note that `--empty=drop` and `--empty=stop` only specify how to handle a commit that was not initially empty, but rather became empty due to a previous commit. Commits that were initially empty will still cause the cherry-pick to fail unless one of `--empty=keep` or `--allow-empty` are specified. \--keep-redundant-commits Deprecated synonym for `--empty=keep`. \--strategy=\<strategy\> Use the given merge strategy. Should only be used once. See the MERGE STRATEGIES section in [git-merge\[1\]](https://git-scm.com/docs/git-merge) for details. \-X\<option\> \--strategy-option=\<option\> Pass the merge strategy-specific option through to the merge strategy. See [git-merge\[1\]](https://git-scm.com/docs/git-merge) for details. `--rerere-autoupdate` `--no-rerere-autoupdate` After the rerere mechanism reuses a recorded resolution on the current conflict to update the files in the working tree, allow it to also update the index with the result of resolution. `--no-rerere-autoupdate` is a good way to double-check what `rerere` did and catch potential mismerges, before committing the result to the index with a separate `git` `add`. ## SEQUENCER SUBCOMMANDS \--continue Continue the operation in progress using the information in `.git/sequencer`. Can be used to continue after resolving conflicts in a failed cherry-pick or revert. \--skip Skip the current commit and continue with the rest of the sequence. \--quit Forget about the current operation in progress. Can be used to clear the sequencer state after a failed cherry-pick or revert. \--abort Cancel the operation and return to the pre-sequence state. ## EXAMPLES `git` `cherry-pick` `master` Apply the change introduced by the commit at the tip of the master branch and create a new commit with this change. `git` `cherry-pick` `..master` `git` `cherry-pick` `^HEAD` `master` Apply the changes introduced by all commits that are ancestors of master but not of HEAD to produce new commits. `git` `cherry-pick` `maint` `next` `^master` `git` `cherry-pick` `maint` `master..next` Apply the changes introduced by all commits that are ancestors of maint or next, but not master or any of its ancestors. Note that the latter does not mean `maint` and everything between `master` and `next`; specifically, `maint` will not be used if it is included in `master`. `git` `cherry-pick` `master~4` `master~2` Apply the changes introduced by the fifth and third last commits pointed to by master and create 2 new commits with these changes. `git` `cherry-pick` `-n` `master~1` `next` Apply to the working tree and the index the changes introduced by the second last commit pointed to by master and by the last commit pointed to by next, but do not create any commit with these changes. `git` `cherry-pick` `--ff` `..next` If history is linear and HEAD is an ancestor of next, update the working tree and advance the HEAD pointer to match next. Otherwise, apply the changes introduced by those commits that are in next but not HEAD to the current branch, creating a new commit for each new change. `git` `rev-list` `--reverse` `master` `--` `README` \\| `git` `cherry-pick` `-n` `--stdin` Apply the changes introduced by all commits on the master branch that touched README to the working tree and index, so the result can be inspected and made into a single new commit if suitable. The following sequence attempts to backport a patch, bails out because the code the patch applies to has changed too much, and then tries again, this time exercising more care about matching up context lines. ``` $ git cherry-pick topic^ (1) $ git diff (2) $ git cherry-pick --abort (3) $ git cherry-pick -Xpatience topic^ (4) ``` 1. apply the change that would be shown by `git` `show` `topic^`. In this example, the patch does not apply cleanly, so information about the conflict is written to the index and working tree and no new commit results. 2. summarize changes to be reconciled 3. cancel the cherry-pick. In other words, return to the pre-cherry-pick state, preserving any local modifications you had in the working tree. 4. try to apply the change introduced by `topic^` again, spending extra time to avoid mistakes based on incorrectly matching context lines. ## SEE ALSO [git-revert\[1\]](https://git-scm.com/docs/git-revert) ## GIT Part of the [git\[1\]](https://git-scm.com/docs/git) suite ### cherry-pick [About this site](https://git-scm.com/site) Patches, suggestions, and comments are welcome. Git is a member of [Software Freedom Conservancy](https://git-scm.com/sfc)
Readable Markdown	## NAME git-cherry-pick - Apply the changes introduced by some existing commits ## SYNOPSIS ``` git cherry-pick [--edit] [-n] [-m <parent-number>] [-s] [-x] [--ff] [-S[<keyid>]] <commit>… git cherry-pick (--continue \| --skip \| --abort \| --quit) ``` ## DESCRIPTION Given one or more existing commits, apply the change each one introduces, recording a new commit for each. This requires your working tree to be clean (no modifications from the HEAD commit). When it is not obvious how to apply a change, the following happens: 1. The current branch and `HEAD` pointer stay at the last commit successfully made. 2. The `CHERRY_PICK_HEAD` ref is set to point at the commit that introduced the change that is difficult to apply. 3. Paths in which the change applied cleanly are updated both in the index file and in your working tree. 4. For conflicting paths, the index file records up to three versions, as described in the "TRUE MERGE" section of [git-merge\[1\]](https://git-scm.com/docs/git-merge). The working tree files will include a description of the conflict bracketed by the usual conflict markers \<\<\<\<\<\<\< and \>\>\>\>\>\>\>. 5. No other modifications are made. See [git-merge\[1\]](https://git-scm.com/docs/git-merge) for some hints on resolving such conflicts. ## OPTIONS \<commit\>… Commits to cherry-pick. For a more complete list of ways to spell commits, see [gitrevisions\[7\]](https://git-scm.com/docs/gitrevisions). Sets of commits can be passed but no traversal is done by default, as if the `--no-walk` option was specified, see [git-rev-list\[1\]](https://git-scm.com/docs/git-rev-list). Note that specifying a range will feed all \<commit\>… arguments to a single revision walk (see a later example that uses maint master..next). \-e \--edit With this option, git cherry-pick will let you edit the commit message prior to committing. \--cleanup=\<mode\> This option determines how the commit message will be cleaned up before being passed on to the commit machinery. See [git-commit\[1\]](https://git-scm.com/docs/git-commit) for more details. In particular, if the \<mode\> is given a value of `scissors`, scissors will be appended to `MERGE_MSG` before being passed on in the case of a conflict. \-x When recording the commit, append a line that says "(cherry picked from commit …)" to the original commit message in order to indicate which commit this change was cherry-picked from. This is done only for cherry picks without conflicts. Do not use this option if you are cherry-picking from your private branch because the information is useless to the recipient. If on the other hand you are cherry-picking between two publicly visible branches (e.g. backporting a fix to a maintenance branch for an older release from a development branch), adding this information can be useful. \-r It used to be that the command defaulted to do `-x` described above, and `-r` was to disable it. Now the default is not to do `-x` so this option is a no-op. \-m \<parent-number\> \--mainline \<parent-number\> Usually you cannot cherry-pick a merge because you do not know which side of the merge should be considered the mainline. This option specifies the parent number (starting from 1) of the mainline and allows cherry-pick to replay the change relative to the specified parent. \-n \--no-commit Usually the command automatically creates a sequence of commits. This flag applies the changes necessary to cherry-pick each named commit to your working tree and the index, without making any commit. In addition, when this option is used, your index does not have to match the HEAD commit. The cherry-pick is done against the beginning state of your index. This is useful when cherry-picking more than one commits' effect to your index in a row. \-s \--signoff Add a `Signed-off-by` trailer at the end of the commit message. See the signoff option in [git-commit\[1\]](https://git-scm.com/docs/git-commit) for more information. \-S\[\<keyid\>\] \--gpg-sign\[=\<keyid\>\] \--no-gpg-sign GPG-sign commits. The `keyid` argument is optional and defaults to the committer identity; if specified, it must be stuck to the option without a space. `--no-gpg-sign` is useful to countermand both `commit.gpgSign` configuration variable, and earlier `--gpg-sign`. \--ff If the current HEAD is the same as the parent of the cherry-pick’ed commit, then a fast forward to this commit will be performed. \--allow-empty By default, cherry-picking an empty commit will fail, indicating that an explicit invocation of `git` `commit` `--allow-empty` is required. This option overrides that behavior, allowing empty commits to be preserved automatically in a cherry-pick. Note that when "--ff" is in effect, empty commits that meet the "fast-forward" requirement will be kept even without this option. Note also, that use of this option only keeps commits that were initially empty (i.e. the commit recorded the same tree as its parent). Commits which are made empty due to a previous commit will cause the cherry-pick to fail. To force the inclusion of those commits, use `--empty=keep`. \--allow-empty-message By default, cherry-picking a commit with an empty message will fail. This option overrides that behavior, allowing commits with empty messages to be cherry picked. \--empty=(drop\\|keep\\|stop) How to handle commits being cherry-picked that are redundant with changes already in the current history. `drop` The commit will be dropped. `keep` The commit will be kept. Implies `--allow-empty`. `stop` The cherry-pick will stop when the commit is applied, allowing you to examine the commit. This is the default behavior. Note that `--empty=drop` and `--empty=stop` only specify how to handle a commit that was not initially empty, but rather became empty due to a previous commit. Commits that were initially empty will still cause the cherry-pick to fail unless one of `--empty=keep` or `--allow-empty` are specified. \--keep-redundant-commits Deprecated synonym for `--empty=keep`. \--strategy=\<strategy\> Use the given merge strategy. Should only be used once. See the MERGE STRATEGIES section in [git-merge\[1\]](https://git-scm.com/docs/git-merge) for details. \-X\<option\> \--strategy-option=\<option\> Pass the merge strategy-specific option through to the merge strategy. See [git-merge\[1\]](https://git-scm.com/docs/git-merge) for details. `--rerere-autoupdate` `--no-rerere-autoupdate` After the rerere mechanism reuses a recorded resolution on the current conflict to update the files in the working tree, allow it to also update the index with the result of resolution. `--no-rerere-autoupdate` is a good way to double-check what `rerere` did and catch potential mismerges, before committing the result to the index with a separate `git` `add`. ## SEQUENCER SUBCOMMANDS \--continue Continue the operation in progress using the information in `.git/sequencer`. Can be used to continue after resolving conflicts in a failed cherry-pick or revert. \--skip Skip the current commit and continue with the rest of the sequence. \--quit Forget about the current operation in progress. Can be used to clear the sequencer state after a failed cherry-pick or revert. \--abort Cancel the operation and return to the pre-sequence state. ## EXAMPLES `git` `cherry-pick` `master` Apply the change introduced by the commit at the tip of the master branch and create a new commit with this change. `git` `cherry-pick` `..master` `git` `cherry-pick` `^HEAD` `master` Apply the changes introduced by all commits that are ancestors of master but not of HEAD to produce new commits. `git` `cherry-pick` `maint` `next` `^master` `git` `cherry-pick` `maint` `master..next` Apply the changes introduced by all commits that are ancestors of maint or next, but not master or any of its ancestors. Note that the latter does not mean `maint` and everything between `master` and `next`; specifically, `maint` will not be used if it is included in `master`. `git` `cherry-pick` `master~4` `master~2` Apply the changes introduced by the fifth and third last commits pointed to by master and create 2 new commits with these changes. `git` `cherry-pick` `-n` `master~1` `next` Apply to the working tree and the index the changes introduced by the second last commit pointed to by master and by the last commit pointed to by next, but do not create any commit with these changes. `git` `cherry-pick` `--ff` `..next` If history is linear and HEAD is an ancestor of next, update the working tree and advance the HEAD pointer to match next. Otherwise, apply the changes introduced by those commits that are in next but not HEAD to the current branch, creating a new commit for each new change. `git` `rev-list` `--reverse` `master` `--` `README` \\| `git` `cherry-pick` `-n` `--stdin` Apply the changes introduced by all commits on the master branch that touched README to the working tree and index, so the result can be inspected and made into a single new commit if suitable. The following sequence attempts to backport a patch, bails out because the code the patch applies to has changed too much, and then tries again, this time exercising more care about matching up context lines. ``` $ git cherry-pick topic^ (1) $ git diff (2) $ git cherry-pick --abort (3) $ git cherry-pick -Xpatience topic^ (4) ``` 1. apply the change that would be shown by `git` `show` `topic^`. In this example, the patch does not apply cleanly, so information about the conflict is written to the index and working tree and no new commit results. 2. summarize changes to be reconciled 3. cancel the cherry-pick. In other words, return to the pre-cherry-pick state, preserving any local modifications you had in the working tree. 4. try to apply the change introduced by `topic^` again, spending extra time to avoid mistakes based on incorrectly matching context lines.
Shard	54 (laksa)
Root Hash	7104038400628677254
Unparsed URL	com,git-scm!/docs/git-cherry-pick s443