ship

Ship

Push the branch and open a GitHub PR via gh, with title and body built from the commits.

Even solo, a PR is worth it: it runs CI, gives a clean diff to skim before merging, and leaves a durable record. This uses the gh CLI.

Input (optional flags):

• --draft → open the PR as a draft
• --base <branch> → target branch (default: BASE_BRANCH / main)
• --merge → after the PR is created and checks pass, merge it (squash)

---

Step 0 — Pre-flight

command -v gh >/dev/null || { echo "[ERROR] gh CLI not installed: https://cli.github.com"; exit 1; }
gh auth status >/dev/null 2>&1 || { echo "[ERROR] Run: gh auth login"; exit 1; }

BRANCH=$(git symbolic-ref --short HEAD 2>/dev/null || true)   # empty when detached
BASE="${BASE_BRANCH:-main}"
[ -n "$BRANCH" ] || { echo "[ERROR] Detached HEAD — check out a branch before shipping."; exit 1; }
case "$BRANCH" in main|master|"$BASE") echo "[ERROR] On base branch '$BRANCH' — nothing to ship. Create a feature branch."; exit 1;; esac

# Anything uncommitted? Ship works on commits, not the working tree.
[ -n "$(git status --porcelain)" ] && echo "[WARN] You have uncommitted changes. Run /commit first, or they won't be in this PR."

git fetch origin --quiet 2>/dev/null || true
AHEAD=$(git rev-list --count "origin/$BASE..HEAD" 2>/dev/null || echo "?")
[ "$AHEAD" = "0" ] && { echo "[ERROR] No commits ahead of $BASE. Nothing to ship."; exit 1; }

Step 1 — Push

git push -u origin "$BRANCH"

If the push is rejected (remote has newer commits): offer git pull --rebase origin "$BRANCH" then push again. Never plain --force; if a rebase genuinely requires it, use --force-with-lease and confirm with the developer first.

Step 2 — Reuse an existing PR if there is one

EXISTING=$(gh pr view "$BRANCH" --json url -q .url 2>/dev/null)
if [ -n "$EXISTING" ]; then
  echo "[SHIP] PR already exists: $EXISTING (the push updated it)."
  # Skip creation; go to Step 5 (optional merge).
fi