A GitHub CLI extension to cherry-pick a PR's merged commit based on target branch.

• It will be useful when you are using to cherry-pick a PR, which is merged to the main branch, to the release branch.

gh extension install 134130/gh-cherry-pick

• gh cherry-pick -pr <pr_number> -onto <target_branch> [-merge auto|squash|rebase] [-push] [-worktree] to cherry-pick a PR based on target branch. It determines the merge strategy based on the original PR's merge strategy.
• gh cherry-pick -pr <pr_number> -onto <target_branch> -merge squash to cherry-pick a PR's merged commit based on target branch.
• gh cherry-pick -pr <pr_number> -onto <target_branch> -merge rebase to cherry-pick all the commits from a PR based on target branch.

The --worktree flag lets you run cherry-pick without a clean local working tree. Instead of operating on your current repository, it clones the repository to an OS temp directory ($TMPDIR/gh-cherry-pick/<owner>/<repo>) and runs all operations there. On subsequent runs, the cached clone is reused.

This is useful when:

• Your working tree has uncommitted changes you don't want to stash
• You want to cherry-pick from any directory, not just inside the repository

# First run: clones the repository to the temp cache
gh cherry-pick -pr 123 -onto release/1.0 --worktree

# Subsequent runs: reuses the cached clone
gh cherry-pick -pr 456 -onto release/1.0 --worktree --push

• gh-domino - A GitHub CLI extension to rebase stacked pull requests
• gh-poi - A GitHub CLI extension to safely clean up local branches you no longer need

• In case one wants to base on a branch being squash-merged into main and avoid git showing conflicts, one can use magic-merge-commit to create a merge commit satisfying git and enabling a clean merge of main again.