Most popular
Validate SQL migrations on every PR push
When commits land on a migration PR, list pending Supabase migrations and comment diff summary on the pull request.
When GitHub: Pull request opened happens, do Supabase: Apply migration.
When this happens in one app, do this in the other. Try it on Hub to connect both apps and run the pair.
Most popular
When commits land on a migration PR, list pending Supabase migrations and comment diff summary on the pull request.
When a migration PR merges to main, apply the new migration to production Supabase.
When a migration PR opens, fetch the migration file details and post setup notes for reviewers.
When a GitHub check fails on db-migrate, pull recent Supabase project logs into the PR thread.
When the schema workflow completes on main, regenerate Supabase TypeScript types and open a follow-up PR comment link.
When a PR updates without matching migration history, submit a GitHub review requesting reorder fixes.
Use Corsair's MCP with your agent
The agent searches both apps before it answers.
Is migration 20250318_user_roles safe to merge today?
Code hosting platform for repositories, issues, pull requests, and developer workflows.
Open-source Firebase alternative with Postgres, auth, storage, and realtime backend services.
Yes. Corsair is built with a REST API. This means you can build agents, knowledge bases, interfaces, and workflows.
Yes. Connect both apps once, then validate migration PRs, apply changes on merge, and pull Supabase logs into failed checks.
Migration comments on PRs, apply-on-merge, type generation after schema changes, check failure diagnostics, and agent review of migration order.
Yes. GitHub pull request, check run, and workflow run events drive typed automations against Supabase migration APIs.