Git Workflow

Branch Strategy

Single developer workflow with 4 persistent branches, each mapped to an environment:

Flow direction: dev → test → pprd → prod

Work happens on dev (or short-lived feature branches off dev). Code must pass all CI gates at each stage before being promoted. No direct pushes to prod.

Branch Protection Rules

Database Per Environment

All environments use Neon DB branches within a single Neon project — no separate paid projects needed.

Prod → pprd Data Replication

Every 24 hours, a GitHub Actions cron job uses the Neon Branch Reset API to sync pprd from prod.

This is faster than pg_dump / pg_restore because Neon branching is a near-instant copy-on-write operation at the storage layer.

# .github/workflows/replicate-prod-to-pprd.yml
on:
  schedule:
    - cron: '0 1 * * *'  # 1 AM UTC daily

CI/CD Pipeline

Gates are cumulative — each stage adds checks on top of the previous one.

✅ Lint + Format (Biome + Ultracite)
✅ Type check (tsc --noEmit)
✅ Unit tests (Vitest)

✅ Lint + Format
✅ Type check
✅ Unit tests
✅ Integration tests (Neon test branch)
✅ Playwright E2E tests
✅ Lighthouse CI (performance ≥ 95; accessibility, best practices, SEO = 100)

✅ All tests from test branch
✅ k6 load test against pprd environment
✅ OWASP ZAP security scan
✅ Smoke test Playwright suite

✅ All CI gates passing
✅ Manual approval required
🚀 Deploy to Cloudflare Workers (OpenNext adapter)

Commit Conventions

Use Conventional Commits for clean history and automatic changelog generation:

feat: add booking confirmation email
fix: correct availability calculation for same-day slots
chore: update dependencies
docs: update testing plan
test: add E2E test for admin booking flow
refactor: extract pricing logic to service layer
perf: cache service catalog in Cloudflare KV
security: add rate limiting to /api/leads

Pre-Commit Hooks

Every git commit automatically runs Biome lint + format on staged files via Husky + lint-staged:

# What runs on every commit (~200ms):
biome check --write --staged

This catches formatting issues and obvious lint errors before they ever reach CI — saving pipeline minutes and avoiding "fix lint" commits.

Secrets Management

Deployment

Weekly Backup

Every Sunday at 2 AM UTC, a GitHub Actions workflow:

Related

• Testing — Full CI gate specifications
• Deployment — Platform configuration details
• Environment Variables — All secrets and their purpose