CI/CD Pipeline

Push to Deploy

Every push to main or staging triggers the test pipeline — TypeScript type-checking across both admin-ui and memory-mcp, unit tests, Convex function tests, and integration tests against a real Convex service container. Pushes to main run tests only; they do not build or deploy.

Staging: Auto-Deploy

Pushes to the staging branch build Docker images, push them to GHCR with the :staging tag, and SSH into the staging droplet to pull and restart. The whole cycle takes roughly four minutes. This is the primary development workflow — merge to staging, watch it deploy, verify on staging.collecthive.ai.

Production: Manual Gate

Production deploys require a manual workflow_dispatch trigger. There is no automated rollback mechanism yet, so a human confirms the staging build is healthy before promoting. The deploy process is identical — build :latest images, pull, and restart — but the trigger is deliberate.

PR Extras

Pull requests get additional scrutiny: Playwright smoke tests against the staging environment, Semgrep static analysis, and GitHub Copilot code review. These run in parallel and must all pass before merge.