# /ship — Autonomous end-to-end feature shipping Ship a feature from implementation to open MR, RC tag, and dev deploy. Runs autonomously and only interrupts at explicit checkpoints. ## Version bumping rules - Backend version lives in `bora/pyproject.toml` — bump patch for fixes, minor for features. - Commit message format: `[BORA X.Y.Z] : ` (e.g. `[BORA 0.17.2] feat: csv export auth`) - RC tag format: `rc-bora-X.Y.Z` — triggers build + deploy to `central-dev` only. - Stable tag format: `stable-bora-X.Y.Z` — triggers build + deploy to all `central-pro` tenants. Apply manually after RC validation. - Branch format: `feat/` for features, `fix/` for fixes. ## MR description structure ``` ## Problem ## Solution ## Testing ## Risk ``` ## Pipeline Use TodoWrite to track every step. Mark each done before moving to the next. ### Checkpoint 1 — Plan (WAIT FOR APPROVAL) - Use ExitPlanMode: list files to change, approach, version bump level, migration needed (yes/no). - Do NOT write any code until approved. ### Step 2 — Branch & implement - **Always create a NEW branch.** Never ship from whatever branch the user happens to be on, even if it looks empty or related. The branch name must match the feature: `feat/` or `fix/`. - Procedure: 1. If there are uncommitted changes for THIS feature, stash them: `git stash push -u -m ship-wip`. 2. `git fetch origin && git checkout main && git pull --ff-only origin main`. 3. `git checkout -b feat/` (or `fix/`). 4. Restore the stash if you made one: `git stash pop`. - Verify before continuing: `git rev-parse --abbrev-ref HEAD` returns the new branch, and `git log origin/main..HEAD` is empty (no commits yet). - Implement across backend (`bora/`) and frontend (`bora-frontend/`) as needed. - Follow all CLAUDE.md conventions: no scope creep, no None guards, no optional dependencies unless the feature requires it. - Never hardcode secrets or tokens — reference them via ExternalSecrets or env vars. ### Step 3 — Tests - Backend: write/update pytest tests, run `pytest bora/tests/ -x` until green. - Frontend: run `npx tsc --noEmit` from `bora-frontend/` after any `.ts`/`.tsx` edits. - Show test output before proceeding. ### Step 4 — Version bump - Bump `bora/pyproject.toml` version following semver. - Patch for fixes, minor for new features. ### Step 5 — Commit & MR - Stage only relevant files (never `git add .`). - Commit: `[BORA X.Y.Z] : ` - **Push the branch first:** `git push -u origin ` — verify it succeeds before proceeding. - **Then** open the MR: `glab mr create --target-branch main --remove-source-branch --squash-before-merge` using the MR description structure above. The `--squash-before-merge` flag pre-selects squash on the MR so main keeps a clean one-commit-per-feature history. - After MR creation, verify commits are visible: `glab mr view --output json | jq -r '.diff_refs'` should reference the pushed commits, not be empty. ### Step 6 — CI polling (up to 3 auto-fix attempts) - Poll pipeline status every 30s using `glab ci status`. - On each poll, also check for merge conflicts: `glab mr view --output json | jq -r '.has_conflicts'`. If `true`, STOP and report — do not attempt to fix conflicts autonomously. - If pipeline failed: read job logs, diagnose, push a fix. Repeat up to 3 times autonomously. - On the 4th failure: STOP and report to user with full diagnosis — do not attempt further fixes. ### Step 7 — RC tag & deploy - Before pushing the RC tag, check for merge conflicts: `glab mr view --output json | jq -r '.has_conflicts'`. If `true`, STOP and report — do not push the tag. - Once MR CI is green and no conflicts, push the RC tag on the current branch HEAD: ``` git tag rc-bora-X.Y.Z && git push origin rc-bora-X.Y.Z ``` - Poll the tag's pipeline with `glab ci status --ref rc-bora-X.Y.Z` every 30s until all jobs finish. - Report deploy job results (build + `deploy:bora:central-dev` + `deploy:bora-frontend:central-dev`). - If the tag pipeline fails: report the failed job logs and stop — do not auto-retry tag pipelines. ### Checkpoint 2 — Done (REPORT BACK) - Report: MR link, MR CI status, RC tag, tag pipeline status (build + dev deploy jobs). - Remind: **squash-merge the MR** (the squash option is pre-selected on creation), then push `stable-bora-X.Y.Z` on main to deploy to prod. ## Feature to ship $ARGUMENTS