Processes
Delivery workflow
How we build, review, and deliver changes.
Purpose
Keep delivery consistent, low-risk, and easy to audit.
Branching
- Trunk-based development with short-lived branches.
- One Linear issue per branch and per PR.
- Prefer the suggested branch name from Linear.
Pull requests
- Keep PRs small and focused.
- All required checks and approvals must pass before merge:
- Tests
- Linting
- CodeQL
- Security checks
- Required reviewer approvals (including code owner when applicable)
- Documentation changes should ship in the same PR when behavior changes.
Feature flags
- Use Statsig for feature flags.
- Default new flags to off and enable gradually.
Hotfixes
- Same workflow as normal changes: issue -> branch -> PR -> checks -> merge.
Last updated on