Branching Governance and Conventions
Branching strategies establish consistent naming patterns and isolate active development from production-ready code.
In GitHub, long-lived default branches are protected from direct commits to preserve release stability.
Contributors must isolate changes in short-lived feature or bugfix branches adhering to standardized naming prefixes:
- feature/: Work supporting new capabilities, APIs, or major documentation updates.
- fix/: Targeted repairs for reported defects or incorrect guidance.
- docs/: Minor prose improvements, typo corrections, or maintenance.