CI/CD Pipeline

Overview

Set up continuous integration and deployment with GitHub Actions, build verification, and deployment gates.

When to Use

• Setting up CI/CD from scratch
• Adding build checks to PRs
• Configuring automated test runs
• Production deployment automation

Workflow

Phase 1: CI Workflow

.github/workflows/ci.yml:

yaml
1name: CI
2on:
3  push:
4    branches: [main]
5  pull_request:
6    branches: [main]
7
8jobs:
9  build:
10    runs-on: ubuntu-latest
11    steps:
12      - uses: actions/checkout@v4
13      - uses: actions/setup-node@v4
14        with:
15          node-version: 20
16          cache: npm
17      - run: npm ci
18      - run: npm run lint
19      - run: npm run build
20      - run: npm run test
21
22  edge-functions:
23    runs-on: ubuntu-latest
24    steps:
25      - uses: actions/checkout@v4
26      - uses: denoland/setup-deno@v2
27      - run: deno check supabase/functions/*/index.ts

Phase 2: Deploy Workflow

yaml
1  deploy:
2    needs: [build, edge-functions]
3    if: github.ref == 'refs/heads/main'
4    runs-on: ubuntu-latest
5    steps:
6      - uses: actions/checkout@v4
7      - uses: actions/setup-node@v4
8        with: { node-version: 20, cache: npm }
9      - run: npm ci && npm run build
10      # Deploy to hosting + edge functions

Phase 3: Branch Protection

1. Require CI pass before merge
2. Require PR review
3. No force push to main

Checklist

• CI runs on push + PRs
• Build, lint, test steps
• Edge function type check
• Deploy only on main after checks pass
• Secrets in GitHub Actions secrets
• Branch protection rules enabled