Tool / A post-checkout hook creates a sub-second, scale-to-zero database branch for every new worktree. GitHub Actions create one per PR for a preview app and post a schema diff. Branches are never merged back: schema changes travel as migrations in code.
Lakebase branching
Databricks' copy-on-write Postgres branches, wired to a worktree hook so each agent gets its own database.
The summary describes what the project says it does; inclusion is not an endorsement.
An explicit answer to the "reconcile isolated results" question for data: don't merge data branches, promote migrations.
- Isolate
- Integrate
AI-drafted