Cherry Pick

From the results, suggest the most recent rc-minor-fleet-v* branch as the default. If patch branches also exist, mention them as alternatives. Always ask the user to confirm the target RC branch before proceeding.

Step 3: Get the merge commit and GitHub username

1. Get the PR title:

   gh pr view <PR_NUMBER> --json title --jq .title
   

2. Get the merge commit SHA:

   gh pr view <PR_NUMBER> --json mergeCommit --jq .mergeCommit.oid
   

   If this returns null or an empty value, the PR is not yet merged. Tell the user and stop.
3. Get the GitHub username: gh api user --jq .login

Step 4: Cherry-pick onto a new branch

1. Create a new branch off the RC branch:

   git checkout -b <github-username>/<short-description>-cp origin/<rc-branch>
   

   Derive <short-description> from the PR title (lowercase, hyphens, keep it short — 3-5 words max).
2. Check whether the commit is a merge commit by inspecting its parents:

   git rev-list --parents -n 1 <merge-commit-SHA>
   

   If the commit has multiple parents, run:

   git cherry-pick -m 1 <merge-commit-SHA>
   

   Otherwise (squash-merged or rebased), run:

   git cherry-pick <merge-commit-SHA>
   

3. If there are conflicts, stop and tell the user which files conflict. Do NOT attempt to resolve them automatically.

Step 5: Push and open PR

1. Push the branch: git push -u origin HEAD
2. Open a PR targeting the RC branch (NOT main):

   gh pr create --base <rc-branch> --title "Cherry-pick #<PR_NUMBER>: <original-title>" --body "$(cat <<'EOF'
   Cherry-pick of #<PR_NUMBER> into the RC branch.
   EOF
   )"
   

3. Report the PR URL to the user.