pr

Create Pull Request

Create a PR with the correct title format, description, and JIRA reference.

Step 1: Validate PR Title

Title must match the CI-enforced regex (set via $PR_TITLE_PATTERN env var):

${PR_TITLE_PATTERN:-^(?:\[redhat-[0-9]+\.[0-9]+\] )?(?:PROJQUAY-[0-9]+|QUAYIO-[0-9]+|NO-ISSUE): [a-z]+(?:\([^)]+\))?: .+$}

Examples:

• PROJQUAY-1234: fix(api): add pagination to tag listing
• NO-ISSUE: chore: update dependencies
• [redhat-3.12] PROJQUAY-1234: fix(api): backport tag pagination

bash .claude/scripts/validate-pr-title.sh "PROJQUAY-1234: fix(api): description here"

Step 2: Build Description

Read the template at .claude/templates/pr-description.md. Fill in:

• Summary: What this PR does
• Root Cause / Rationale: Why
• Changes: What changed
• Test Plan: How to verify
• JIRA Link: ${JIRA_BROWSE_URL:-https://redhat.atlassian.net/browse}/<TICKET-KEY>
• Backport: Required or not (from /start)

Step 3: Ambient Session Metadata

Check if this PR is being created from an ambient session:

echo $AGENTIC_SESSION_NAME

• If AGENTIC_SESSION_NAME is set: populate the ## Automation section with the session ID value.
• If empty/unset: remove the ## Automation section entirely.

Write the filled template to /tmp/pr-body.md.

Step 4: Create PR

If AGENTIC_SESSION_NAME was set, include --label "${AMBIENT_SESSION_LABEL:-ambient-session}":

gh pr create \
  --title "<TICKET>: type(scope): description" \
  --body "$(cat /tmp/pr-body.md)" \
  --base ${PRIMARY_BRANCH:-master} \
  --label "${AMBIENT_SESSION_LABEL:-ambient-session}"

For manual PRs (no ambient session), omit the --label flag.

Step 5: Post-PR

After creation, CI bots will validate the JIRA reference and check status.

Always run /poll <PR#> immediately after PR creation — do not ask the user.