Overview
Purpose
This document establishes standardized workflows for the development team to ensure:
- No overlapping work: Developers work on isolated branches for specific features
- Code quality: All changes are reviewed before merging
- Clear history: Commit messages and PR descriptions provide context
- Non-breaking changes: Main branch remains stable and deployable
- Consistent AI assistance: AI assistants follow team standards
Core Principles
- Main branch is always deployable - Never commit breaking changes directly to main
- One feature, one branch - Each feature/bug/enhancement gets its own branch
- Review before merge - All code must be reviewed by at least one other person
- Clear communication - Commit messages and PRs tell the story of why changes were made