backport

Backport PR

Backport merged PR #$ARGUMENTS[0] to a release branch.

• PR number: $ARGUMENTS[0]
• Branch (optional): $ARGUMENTS[1]

Step 1: Verify Merged

gh pr view "$ARGUMENTS[0]" --json state,mergedAt,title

The PR must be merged. If not, inform the user and stop.

Step 2: Determine Branch

If $ARGUMENTS[1] is provided, use it as the target branch.

Otherwise, extract the JIRA ticket key from the PR title and check Target Version:

bash .claude/scripts/jira-ops.sh check-version <TICKET-KEY>

Map Target Version to release branch. The mapping is project-specific — consult the project's release branch naming convention. Ask the user if the mapping is ambiguous.

Step 3: Trigger Cherry-Pick

gh pr comment "$ARGUMENTS[0]" --body "${CHERRYPICK_COMMAND:-/cherrypick} <BRANCH>"

Step 4: Confirm

Report:

• Cherry-pick command posted on PR #$ARGUMENTS[0]
• Target branch
• The cherry-pick bot will create a backport PR automatically
• Monitor the backport PR for CI results

Manual Backport (if cherry-pick bot fails)

The bot can fail due to merge conflicts or missing labels. When that happens, create the backport manually:

git fetch origin
git checkout -b <BRANCH>-backport-<PR_NUMBER> origin/<BRANCH>
git cherry-pick -m 1 <MERGE_COMMIT_SHA>

If there are conflicts:

1. Resolve each conflict manually
2. git add the resolved files
3. git cherry-pick --continue

Then push and create the backport PR:

git push -u origin <BRANCH>-backport-<PR_NUMBER>
gh pr create \
  --title "[<BRANCH>] <ORIGINAL_PR_TITLE>" \
  --body "Backport of #$ARGUMENTS[0]" \
  --base <BRANCH>