Git Workflow
We follow trunk-based development with short-lived feature branches. All work branches frommain and merges back within a day or two. Long-running branches are discouraged — if a feature is too large, break it into smaller increments behind feature flags. Every merge to main should leave the codebase in a deployable state.
Branch Naming
feature/description— new featuresfix/description— bug fixeschore/description— maintenancedocs/description— documentation
Code Review
All changes require at least one approval
Reviews should be completed within 4 hours
Focus on correctness and clarity, not style
Use conventional comments (suggestion, issue, nit)
Authors merge their own PRs after approval
CI/CD Pipeline
Build
TypeScript compilation, dependency audit, bundle analysis
Test
Unit tests via Vitest, E2E tests via Playwright, coverage gates
Lint
ESLint, Prettier, type checking
Deploy
Automated staging deploy, manual production promotion
Testing Requirements
| Test Type | Required | Coverage Target |
|---|---|---|
| Unit tests | Yes | 80% lines |
| Integration tests | Yes | Critical paths |
| E2E tests | Yes | Core user flows |
| Performance tests | No | Key endpoints only |
Definition of Done
Code reviewed and approved
All tests passing
No TypeScript errors
Documentation updated if needed
Deployed to staging and verified
Product owner sign-off for features