Branch Overview

Understanding the branching model used in the vibe coding platform.

Branch Types

Our repository uses three types of branches:

Main Branch

Branch	Purpose
`main`	Production - what's currently live

Working Branches

Branch	Purpose
`feature/*`	New features and changes
`hotfix/*`	Urgent production fixes

Branch Flow

When you open a Pull Request to main, a preview deploy automatically runs with a dedicated database branch for testing.

Branch flow diagramtext

feature/new-feature
  ↓
  PR to main
  ↓
[CI checks run + Preview deploy: staging + Neon DB branch]
  ↓
[PR comment: Preview URL + Neon branch]
  ↓
  Developer approves → Merge to main
  ↓
[Auto-deploy to production + Migrations on Neon main]

Rules

✅ Always create branches from main
✅ Always use Pull Requests
✅ Test on preview URL before merging
❌ Never push directly to main
❌ Never merge without passing CI checks

Quiz

Which branch represents what's currently live in production?

mainfeaturehotfixstaging