{
    "content": [
        {
            "type": "text",
            "text": "# git-cherry-pick (man)\n\n## NAME\n\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[-S[<keyid>]] <commit>...\ngit cherry-pick (--continue | --skip | --abort | --quit)\n\n## DESCRIPTION\n\nGiven one or more existing commits, apply the change each one introduces, recording a new\ncommit for each. This requires your working tree to be clean (no modifications from the HEAD\ncommit).\n\n## TLDR\n\n> Apply the changes introduced by existing commits to the current branch.\n\n- Apply a commit to the current branch:\n  `git cherry-pick {{commit}}`\n- Apply a range of commits to the current branch (see also: `git rebase --onto`):\n  `git cherry-pick {{start_commit}}~..{{end_commit}}`\n- Apply multiple (non-sequential) commits to the current branch:\n  `git cherry-pick {{commit1 commit2 ...}}`\n- Add the changes of a commit to the working directory, without creating a commit:\n  `git cherry-pick {{-n|--no-commit}} {{commit}}`\n\n*Source: tldr-pages*\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS**\n- **DESCRIPTION**\n- **OPTIONS** (10 subsections)\n- **SEQUENCER SUBCOMMANDS** (4 subsections)\n- **EXAMPLES** (5 subsections)\n- **SEE ALSO**\n- **GIT**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n"
        }
    ],
    "structuredContent": {
        "command": "git-cherry-pick",
        "section": "",
        "mode": "man",
        "summary": "git-cherry-pick - Apply the changes introduced by some existing commits",
        "synopsis": "git cherry-pick [--edit] [-n] [-m parent-number] [-s] [-x] [--ff]\n[-S[<keyid>]] <commit>...\ngit cherry-pick (--continue | --skip | --abort | --quit)",
        "tldr_summary": "Apply the changes introduced by existing commits to the current branch.",
        "tldr_examples": [
            {
                "description": "Apply a commit to the current branch",
                "command": "git cherry-pick {{commit}}"
            },
            {
                "description": "Apply a range of commits to the current branch (see also: `git rebase --onto`)",
                "command": "git cherry-pick {{start_commit}}~..{{end_commit}}"
            },
            {
                "description": "Apply multiple (non-sequential) commits to the current branch",
                "command": "git cherry-pick {{commit1 commit2 ...}}"
            },
            {
                "description": "Add the changes of a commit to the working directory, without creating a commit",
                "command": "git cherry-pick {{-n|--no-commit}} {{commit}}"
            }
        ],
        "tldr_source": "official",
        "flags": [
            {
                "flag": "-e",
                "long": "--edit",
                "arg": null,
                "description": "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 MERGEMSG before being passed on in the case of a conflict."
            },
            {
                "flag": "-x",
                "long": null,
                "arg": null,
                "description": "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."
            },
            {
                "flag": "-r",
                "long": null,
                "arg": null,
                "description": "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."
            },
            {
                "flag": "-n",
                "long": "--no-commit",
                "arg": null,
                "description": "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."
            },
            {
                "flag": "-s",
                "long": "--signoff",
                "arg": null,
                "description": "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."
            },
            {
                "flag": "",
                "long": "--ff",
                "arg": null,
                "description": "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."
            },
            {
                "flag": "",
                "long": "--allow-empty",
                "arg": null,
                "description": "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 are dropped. To force the inclusion of those commits use --keep-redundant-commits."
            },
            {
                "flag": "",
                "long": "--allow-empty-message",
                "arg": null,
                "description": "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."
            },
            {
                "flag": "",
                "long": "--keep-redundant-commits",
                "arg": null,
                "description": "If a commit being cherry picked duplicates a commit already in the current history, it will become empty. By default these redundant commits cause cherry-pick to stop so the user can examine the commit. This option overrides that behavior and creates an empty commit object. Implies --allow-empty. --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."
            },
            {
                "flag": "",
                "long": "--no-rerere-autoupdate",
                "arg": null,
                "description": "Allow the rerere mechanism to update the index with the result of auto-conflict resolution if possible."
            }
        ],
        "examples": [
            "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.",
            "Apply the changes introduced by the fifth and third last commits pointed to by master and",
            "create 2 new commits with these changes.",
            "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.",
            "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.",
            "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 reset --merge ORIGHEAD        (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": [
            {
                "name": "git-revert",
                "section": "1",
                "url": "https://www.chedong.com/phpMan.php/man/git-revert/1/json"
            }
        ],
        "section_outline": [
            {
                "name": "NAME",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "SYNOPSIS",
                "lines": 5,
                "subsections": []
            },
            {
                "name": "DESCRIPTION",
                "lines": 22,
                "subsections": []
            },
            {
                "name": "OPTIONS",
                "lines": 7,
                "subsections": [
                    {
                        "name": "-e, --edit",
                        "lines": 9,
                        "flag": "-e",
                        "long": "--edit"
                    },
                    {
                        "name": "-x",
                        "lines": 8,
                        "flag": "-x"
                    },
                    {
                        "name": "-r",
                        "lines": 9,
                        "flag": "-r"
                    },
                    {
                        "name": "-n, --no-commit",
                        "lines": 8,
                        "flag": "-n",
                        "long": "--no-commit"
                    },
                    {
                        "name": "-s, --signoff",
                        "lines": 8,
                        "flag": "-s",
                        "long": "--signoff"
                    },
                    {
                        "name": "--ff",
                        "lines": 3,
                        "long": "--ff"
                    },
                    {
                        "name": "--allow-empty",
                        "lines": 9,
                        "long": "--allow-empty"
                    },
                    {
                        "name": "--allow-empty-message",
                        "lines": 3,
                        "long": "--allow-empty-message"
                    },
                    {
                        "name": "--keep-redundant-commits",
                        "lines": 13,
                        "long": "--keep-redundant-commits"
                    },
                    {
                        "name": "--rerere-autoupdate, --no-rerere-autoupdate",
                        "lines": 3,
                        "long": "--no-rerere-autoupdate"
                    }
                ]
            },
            {
                "name": "SEQUENCER SUBCOMMANDS",
                "lines": 1,
                "subsections": [
                    {
                        "name": "--continue",
                        "lines": 3,
                        "long": "--continue"
                    },
                    {
                        "name": "--skip",
                        "lines": 2,
                        "long": "--skip"
                    },
                    {
                        "name": "--quit",
                        "lines": 3,
                        "long": "--quit"
                    },
                    {
                        "name": "--abort",
                        "lines": 2,
                        "long": "--abort"
                    }
                ]
            },
            {
                "name": "EXAMPLES",
                "lines": 1,
                "subsections": [
                    {
                        "name": "git cherry-pick master",
                        "lines": 13
                    },
                    {
                        "name": "git cherry-pick master~4 master~2",
                        "lines": 3
                    },
                    {
                        "name": "git cherry-pick -n master~1 next",
                        "lines": 4
                    },
                    {
                        "name": "git cherry-pick --ff ..next",
                        "lines": 5
                    },
                    {
                        "name": "git rev-list --reverse master -- README | git cherry-pick -n --stdin",
                        "lines": 23
                    }
                ]
            },
            {
                "name": "SEE ALSO",
                "lines": 2,
                "subsections": []
            },
            {
                "name": "GIT",
                "lines": 5,
                "subsections": []
            }
        ],
        "sections": {
            "NAME": {
                "content": "git-cherry-pick - Apply the changes introduced by some existing commits\n",
                "subsections": []
            },
            "SYNOPSIS": {
                "content": "git cherry-pick [--edit] [-n] [-m parent-number] [-s] [-x] [--ff]\n[-S[<keyid>]] <commit>...\ngit cherry-pick (--continue | --skip | --abort | --quit)\n\n",
                "subsections": []
            },
            "DESCRIPTION": {
                "content": "Given one or more existing commits, apply the change each one introduces, recording a new\ncommit for each. This requires your working tree to be clean (no modifications from the HEAD\ncommit).\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.\n\n2. The CHERRYPICKHEAD ref is set to point at the commit that introduced the change that is\ndifficult to apply.\n\n3. Paths in which the change applied cleanly are updated both in the index file and in your\nworking tree.\n\n4. For conflicting paths, the index file records up to three versions, as described in the\n\"TRUE MERGE\" section of git-merge(1). The working tree files will include a description\nof the conflict bracketed by the usual conflict markers <<<<<<< and >>>>>>>.\n\n5. No other modifications are made.\n\nSee git-merge(1) for some hints on resolving such conflicts.\n",
                "subsections": []
            },
            "OPTIONS": {
                "content": "<commit>...\nCommits to cherry-pick. For a more complete list of ways to spell commits, see\ngitrevisions(7). Sets of commits can be passed but no traversal is done by default, as if\nthe --no-walk option was specified, see git-rev-list(1). Note that specifying a range\nwill feed all <commit>... arguments to a single revision walk (see a later example that\nuses maint master..next).\n",
                "subsections": [
                    {
                        "name": "-e, --edit",
                        "content": "With this option, git cherry-pick will let you edit the commit message prior to\ncommitting.\n\n--cleanup=<mode>\nThis option determines how the commit message will be cleaned up before being passed on\nto the commit machinery. See git-commit(1) for more details. In particular, if the <mode>\nis given a value of scissors, scissors will be appended to MERGEMSG before being passed\non in the case of a conflict.\n",
                        "flag": "-e",
                        "long": "--edit"
                    },
                    {
                        "name": "-x",
                        "content": "When recording the commit, append a line that says \"(cherry picked from commit ...)\" to\nthe original commit message in order to indicate which commit this change was\ncherry-picked from. This is done only for cherry picks without conflicts. Do not use this\noption if you are cherry-picking from your private branch because the information is\nuseless to the recipient. If on the other hand you are cherry-picking between two\npublicly visible branches (e.g. backporting a fix to a maintenance branch for an older\nrelease from a development branch), adding this information can be useful.\n",
                        "flag": "-x"
                    },
                    {
                        "name": "-r",
                        "content": "It used to be that the command defaulted to do -x described above, and -r was to disable\nit. Now the default is not to do -x so this option is a no-op.\n\n-m parent-number, --mainline parent-number\nUsually you cannot cherry-pick a merge because you do not know which side of the merge\nshould be considered the mainline. This option specifies the parent number (starting from\n1) of the mainline and allows cherry-pick to replay the change relative to the specified\nparent.\n",
                        "flag": "-r"
                    },
                    {
                        "name": "-n, --no-commit",
                        "content": "Usually the command automatically creates a sequence of commits. This flag applies the\nchanges necessary to cherry-pick each named commit to your working tree and the index,\nwithout making any commit. In addition, when this option is used, your index does not\nhave to match the HEAD commit. The cherry-pick is done against the beginning state of\nyour index.\n\nThis is useful when cherry-picking more than one commits' effect to your index in a row.\n",
                        "flag": "-n",
                        "long": "--no-commit"
                    },
                    {
                        "name": "-s, --signoff",
                        "content": "Add a Signed-off-by trailer at the end of the commit message. See the signoff option in\ngit-commit(1) for more information.\n\n-S[<keyid>], --gpg-sign[=<keyid>], --no-gpg-sign\nGPG-sign commits. The keyid argument is optional and defaults to the committer identity;\nif specified, it must be stuck to the option without a space.  --no-gpg-sign is useful to\ncountermand both commit.gpgSign configuration variable, and earlier --gpg-sign.\n",
                        "flag": "-s",
                        "long": "--signoff"
                    },
                    {
                        "name": "--ff",
                        "content": "If the current HEAD is the same as the parent of the cherry-pick’ed commit, then a fast\nforward to this commit will be performed.\n",
                        "long": "--ff"
                    },
                    {
                        "name": "--allow-empty",
                        "content": "By default, cherry-picking an empty commit will fail, indicating that an explicit\ninvocation of git commit --allow-empty is required. This option overrides that behavior,\nallowing empty commits to be preserved automatically in a cherry-pick. Note that when\n\"--ff\" is in effect, empty commits that meet the \"fast-forward\" requirement will be kept\neven without this option. Note also, that use of this option only keeps commits that were\ninitially empty (i.e. the commit recorded the same tree as its parent). Commits which are\nmade empty due to a previous commit are dropped. To force the inclusion of those commits\nuse --keep-redundant-commits.\n",
                        "long": "--allow-empty"
                    },
                    {
                        "name": "--allow-empty-message",
                        "content": "By default, cherry-picking a commit with an empty message will fail. This option\noverrides that behavior, allowing commits with empty messages to be cherry picked.\n",
                        "long": "--allow-empty-message"
                    },
                    {
                        "name": "--keep-redundant-commits",
                        "content": "If a commit being cherry picked duplicates a commit already in the current history, it\nwill become empty. By default these redundant commits cause cherry-pick to stop so the\nuser can examine the commit. This option overrides that behavior and creates an empty\ncommit object. Implies --allow-empty.\n\n--strategy=<strategy>\nUse the given merge strategy. Should only be used once. See the MERGE STRATEGIES section\nin git-merge(1) for details.\n\n-X<option>, --strategy-option=<option>\nPass the merge strategy-specific option through to the merge strategy. See git-merge(1)\nfor details.\n",
                        "long": "--keep-redundant-commits"
                    },
                    {
                        "name": "--rerere-autoupdate, --no-rerere-autoupdate",
                        "content": "Allow the rerere mechanism to update the index with the result of auto-conflict\nresolution if possible.\n",
                        "long": "--no-rerere-autoupdate"
                    }
                ]
            },
            "SEQUENCER SUBCOMMANDS": {
                "content": "",
                "subsections": [
                    {
                        "name": "--continue",
                        "content": "Continue the operation in progress using the information in .git/sequencer. Can be used\nto continue after resolving conflicts in a failed cherry-pick or revert.\n",
                        "long": "--continue"
                    },
                    {
                        "name": "--skip",
                        "content": "Skip the current commit and continue with the rest of the sequence.\n",
                        "long": "--skip"
                    },
                    {
                        "name": "--quit",
                        "content": "Forget about the current operation in progress. Can be used to clear the sequencer state\nafter a failed cherry-pick or revert.\n",
                        "long": "--quit"
                    },
                    {
                        "name": "--abort",
                        "content": "Cancel the operation and return to the pre-sequence state.\n",
                        "long": "--abort"
                    }
                ]
            },
            "EXAMPLES": {
                "content": "",
                "subsections": [
                    {
                        "name": "git cherry-pick master",
                        "content": "Apply the change introduced by the commit at the tip of the master branch and create a\nnew commit with this change.\n\ngit cherry-pick ..master, git cherry-pick ^HEAD master\nApply the changes introduced by all commits that are ancestors of master but not of HEAD\nto produce new commits.\n\ngit cherry-pick maint next ^master, git cherry-pick maint master..next\nApply the changes introduced by all commits that are ancestors of maint or next, but not\nmaster or any of its ancestors. Note that the latter does not mean maint and everything\nbetween master and next; specifically, maint will not be used if it is included in\nmaster.\n"
                    },
                    {
                        "name": "git cherry-pick master~4 master~2",
                        "content": "Apply the changes introduced by the fifth and third last commits pointed to by master and\ncreate 2 new commits with these changes.\n"
                    },
                    {
                        "name": "git cherry-pick -n master~1 next",
                        "content": "Apply to the working tree and the index the changes introduced by the second last commit\npointed to by master and by the last commit pointed to by next, but do not create any\ncommit with these changes.\n"
                    },
                    {
                        "name": "git cherry-pick --ff ..next",
                        "content": "If history is linear and HEAD is an ancestor of next, update the working tree and advance\nthe HEAD pointer to match next. Otherwise, apply the changes introduced by those commits\nthat are in next but not HEAD to the current branch, creating a new commit for each new\nchange.\n"
                    },
                    {
                        "name": "git rev-list --reverse master -- README | git cherry-pick -n --stdin",
                        "content": "Apply the changes introduced by all commits on the master branch that touched README to\nthe working tree and index, so the result can be inspected and made into a single new\ncommit if suitable.\n\nThe following sequence attempts to backport a patch, bails out because the code the patch\napplies to has changed too much, and then tries again, this time exercising more care about\nmatching up context lines.\n\n$ git cherry-pick topic^             (1)\n$ git diff                           (2)\n$ git reset --merge ORIGHEAD        (3)\n$ git cherry-pick -Xpatience topic^  (4)\n\n\n1. apply the change that would be shown by git show topic^. In this example, the patch does\nnot apply cleanly, so information about the conflict is written to the index and working tree\nand 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\nany local modifications you had in the working tree.\n4. try to apply the change introduced by topic^ again, spending extra time to avoid mistakes\nbased on incorrectly matching context lines.\n"
                    }
                ]
            },
            "SEE ALSO": {
                "content": "git-revert(1)\n",
                "subsections": []
            },
            "GIT": {
                "content": "Part of the git(1) suite\n\n\n\nGit 2.34.1                                   02/26/2026                           GIT-CHERRY-PICK(1)",
                "subsections": []
            }
        }
    }
}