Branching - Add --with-data option to GitHub integration

[cohlar]

Supabase offers a great branching feature.
While the CLI offers the option create a branch --with-data, this option is not available in the native GitHub integration.
It's be great to have this option in the UI Settings > Integrations > GitHub Integration: a little toggle to include data when creating new branches.

[VectorPeak]

Thanks for the suggestion - this makes sense. The GitHub integration currently creates preview branches without exposing the CLI’s --with-data behavior, so adding a UI toggle for “include data” would be the right shape for this.

One consideration is that data cloning can have cost/performance/security implications depending on project size and contents, so the setting would likely need to be explicit and probably disabled by default.

For now, the workaround is to create the branch via the CLI using:

supabase branches create <branch-name> --with-data

Leaving this open as a feature request for the GitHub integration.

[harrysun2006]

Agree this would be handy. It's CLI-only right now — you can already include data with supabase branches create --with-data (or when creating a persistent branch), so a workaround is to create branches via the CLI instead of the GitHub integration, or seed the branch with a migration/seed file.

A toggle under Settings → Integrations → GitHub is a valid ask — worth upvoting so it gets tracked on the roadmap.

[yakubka]

Good feature request. The --with-data flag is available in the CLI today (supabase db branch create --with-data) but the GitHub integration does not expose it yet. You can work around this by running the CLI step as part of your CI workflow immediately after the branch is created by the integration.

Add a step in your GitHub Actions workflow that runs after the Supabase branch is created:

• name: Seed branch with data
  env:
  SUPABASE_ACCESS_TOKEN: ${{ secrets.SUPABASE_ACCESS_TOKEN }}
  run: |
  BRANCH_NAME="${{ github.head_ref }}"
  supabase db branch create "$BRANCH_NAME" --with-data
  --project-ref ${{ secrets.SUPABASE_PROJECT_ID }} 2>/dev/null || true

The 2>/dev/null || true handles the case where the branch was already created by the integration. This gives you data seeding on every PR branch until the toggle lands in the UI. Upvoted the feature request.