Administrator
|
af2e9e9a1f
|
docs: add comprehensive branch structure documentation
Created detailed branch structure guide for V2 development:
Branch Hierarchy:
- v2-master (production, protected)
└── v2-master-dev (development, protected)
└── feature/v2/* (feature branches)
Documented Branches:
- v2-master: Production-ready code, protected, 100% coverage
- v2-master-dev: Integration/testing, protected, 100% coverage
- feature/v2/*: Feature development, atomic tasks
- feature/v2-prep: Foundation (archived, complete)
Workflow Examples:
- Standard feature development (9 steps)
- Production release process
- Hotfix workflow for urgent fixes
Branch Protection Rules:
- Require PR before merge
- Require 1+ approval
- Require all CI/CD checks pass
- 100% coverage enforced
- No direct commits to protected branches
CI/CD Pipeline:
- Triggers on all branches
- Pre-flight, build, quality, tests, modularity
- Coverage enforcement (fails if < 100%)
- Performance benchmarks
Best Practices:
- DO: TDD, conventional commits, make validate
- DON'T: Direct commits, bypass CI/CD, skip tests
Quick Reference:
- Common commands
- Branch overview table
- Coverage requirements (100% non-negotiable)
Foundation Status: ✅ Complete
Next Phase: Protocol parser implementations
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-Authored-By: Claude <noreply@anthropic.com>
|
2025-11-10 14:57:26 +01:00 |
|