sumologic-documentation: Command for Claude Code

Stage Deploy — Deploy PR to Shared Staging

Deploy a PR branch to the shared Pantheon staging environment for previewing UX/UI changes or other site-wide feature work before merge.

When to use this command

• You're shipping a UX/UI change, new Docusaurus feature, or other site-wide update and need a live environment to validate it before merge.
• A reviewer needs to see the change in context (navigation, theming, layout) rather than as a single article.

For quick, temporary article-level review, use /review-deploy instead — it targets the separate docs-review environment and keeps this slot free for feature work.

Usage

/stage-deploy {pr-number-or-branch}

Examples:

• /stage-deploy 6701
• /stage-deploy docs-update-jira-skill-fields

Staging environment

• URL: https://helpdocs-sumo-logic.pantheonsite.io/help/
• HTTP basic auth protected: Contact the docs team for credentials.
• Single shared slot: Only one PR can be staged at a time. Deploying overwrites the previous deployment.
• Build time: 20–30 minutes after the push triggers the workflow.

Workflow

Step 1: Resolve input to PR number

• If input is numeric: validate the PR exists and is open with gh pr view {number} --json state --jq '.state'.
• If input is a branch name: look up the PR number with gh pr list --head {branch} --json number --jq '.[0].number'.

You need the PR number for the staging branch name, the PR comment, and to fetch the PR's head commit in Step 4. The branch name itself isn't needed for the push — see Step 4 for why.

Step 2: Check for conflicts

git ls-remote --heads origin 'refs/heads/staging/pr-*'

Exclude staging/pr-{number} for the PR you're currently deploying from the results — redeploying the same PR after new commits isn't a conflict with itself, and shouldn't trigger the overwrite comment below on the PR's own thread.

If one or more other staging branches remain, identify who owns each one (gh pr view {n} for every match) and list all of them for the user: