Supabase Branching + CI integration (spike notes)

Documentation Index

Fetch the complete documentation index at: https://docs.encoreos.io/llms.txt

Use this file to discover all available pages before exploring further.

​

Goal

1. Resolve the preview branch (or migration apply status) for a prod → production PR on project srcaoozjkrughebmbvfb.
2. Surface “what will run in prod” in GitHub (check run body, PR comment, or artifact) without leaking secrets.

​

Option A — Supabase CLI in GitHub Actions (current baseline)

• supabase migration list --linked — local vs remote migration filenames (post-link in scripts/supabase/deploy-preflight.ts).
• supabase db diff --linked — requires Docker on the runner; compares linked remote to local migration state (used for dev drift gate).
• Branch-specific subcommands evolve by CLI version; re-check Supabase CLI reference before building “link to preview DB” automation.

​

Option B — Supabase Management API

• Branches: Supabase API docs (branch list, merge status — endpoints and auth scopes change with product releases).
• Typical need: personal access token / org token with permission to read branch metadata for project srcaoozjkrughebmbvfb.

​

Option C — GitHub Check + Dashboard (lowest automation)

• Rely on the Supabase Preview GitHub check from the GitHub integration (see VERCEL_SUPABASE_ENV_ALIGNMENT.md §2.2–§3.2).
• PR automation only posts links to Dashboard branches + migration list from git diff (see scripts/supabase/release-pr-db-summary.ts).

​

Recommendation (until spike is re-run on current product)

1. Require Supabase Preview check on production PRs (branch protection).
2. Use git-based summaries + Dashboard links in CI (supabase-promote-pr.yml).
3. Re-spike Option B when implementing “real Branching diff” comments; keep db push reconcile documented as break-glass in deploy workflow inputs.

​

Related

• MIGRATION_LANES.md — lane inventory + retrofit.
• SUPABASE_MULTI_ENV_SETUP.md — workflow map.