Configure Supabase CI/CD integration with GitHub Actions and testing. Use when setting up automated testing, configuring CI pipelines, or integrating Supabase tests into your build process. Trigger with phrases like "supabase CI", "supabase GitHub Actions", "supabase automated tests", "CI supabase".
/plugin marketplace add jeremylongshore/claude-code-plugins-plus-skills/plugin install supabase-pack@claude-code-plugins-plusThis skill is limited to using the following tools:
Set up CI/CD pipelines for Supabase integrations with automated testing.
Create .github/workflows/supabase-integration.yml:
name: Supabase Integration Tests
on:
push:
branches: [main]
pull_request:
branches: [main]
env:
SUPABASE_API_KEY: ${{ secrets.SUPABASE_API_KEY }}
jobs:
test:
runs-on: ubuntu-latest
env:
SUPABASE_API_KEY: ${{ secrets.SUPABASE_API_KEY }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
cache: 'npm'
- run: npm ci
- run: npm test -- --coverage
- run: npm run test:integration
gh secret set SUPABASE_API_KEY --body "sk_test_***"
describe('Supabase Integration', () => {
it.skipIf(!process.env.SUPABASE_API_KEY)('should connect', async () => {
const client = getSupabaseClient();
const result = await client.healthCheck();
expect(result.status).toBe('ok');
});
});
| Issue | Cause | Solution |
|---|---|---|
| Secret not found | Missing configuration | Add secret via gh secret set |
| Tests timeout | Network issues | Increase timeout or mock |
| Auth failures | Invalid key | Check secret value |
on:
push:
tags: ['v*']
jobs:
release:
runs-on: ubuntu-latest
env:
SUPABASE_API_KEY: ${{ secrets.SUPABASE_API_KEY_PROD }}
steps:
- uses: actions/checkout@v4
- uses: actions/setup-node@v4
with:
node-version: '20'
- run: npm ci
- name: Verify Supabase production readiness
run: npm run test:integration
- run: npm run build
- run: npm publish
required_status_checks:
- "test"
- "supabase-integration"
For deployment patterns, see supabase-deploy-integration.