Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.insforge.dev/llms.txt

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

A branch is a child project with its own Postgres, auth config, storage, edge functions, email templates, realtime channels, and schedules. Merge back when ready or reset and retry. Available on InsForge OSS 2.1.0+.

​
Concepts

Each branch runs on its own EC2 instance, restored from the parent at create time. merge runs a three-way diff against the parent’s create-time state. The branch shares the parent’s JWT_SECRET but gets its own API_KEY. Compute services and frontend deployments do not branch.

​
Usage

Create a branch with full (schema + data) or schema-only (faster, empty user tables). 
npx @insforge/cli branch create feat-billing --mode full
npx @insforge/cli branch list
Preview the merge SQL before applying. 
npx @insforge/cli branch merge feat-billing --dry-run --save-sql ./preview.sql
npx @insforge/cli branch merge feat-billing
Roll back to the create-time snapshot, or delete the branch. 
npx @insforge/cli branch reset feat-billing
npx @insforge/cli branch delete feat-billing

​
Specific usage cases

Use a branch for risky schema migrations, RLS rewrites, OAuth provider swaps, and edge function refactors. Skip it for trivial changes and data backfills (user-data rows are not auto-merged). Merges block on conflicts. Resolve on the branch or reset and retry. Quotas: 3 parent projects per org, 2 active branches per parent, no nesting. A successful merge does not auto-delete the branch.

​
More resources