ci: add GitHub Actions CI/CD with staging + production environments

↗ view on GitHub · Pol Guixe · 2026-05-27 · cb594f35

Adds a single-workflow CI/CD pipeline plus the deploy config it needs:

- .github/workflows/ci-cd.yml: build/lint on every PR; branch-driven deploys
  (staging branch -> staging env, main -> production env). Deploy jobs are
  gated behind their CI job and pick the GitHub Environment from the branch,
  so the same secret names resolve per-environment.
- frontend/wrangler.jsonc: OpenNext/Workers config with named env blocks
  (mike-frontend-staging / mike-frontend-production). Was missing entirely.
- frontend/package.json: deploy:staging / deploy:production scripts.
- backend/railway.json: pins start command and /health check for Railway.
- DEPLOY.md: full runbook (Railway + Cloudflare + Supabase + R2) and the
  CI/CD + two-environment setup guide.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Repository OrigenStudio/mike
Author Pol Guixe <pol@origen.studio>
Authored
Parents d39f5806
Stats 5 files changed , +443
Part of CI/CD deploy pipeline (GitHub Actions, staging + production)

Capture this commit into my fork

Download a Markdown prompt that tells Claude how to port this exact commit into your working tree. Run it via claude -p < capture-commit-cb594f35.md from inside the repo you want the change in.

⬇ Download capture-commit-cb594f35.md