Branch names

Branch names used across all of the organization's repositories should:

• Be lowercased and kebab-cased
• Use the imperative mood with an action that indicates the branch's main accomplishment
• Contain one prefix from the list below separated by a forward slash

Prefixes:

• "features": For new functionality
• "fixes": For bug fixes
• "improvements": For improvements to existing functionality
• "refactors": For non-functional changes intended to improve the quality of code

Valid branch names:

• "fixes/resolve-race-condition"
• "features/add-widget"
• "improvements/increase-logo-size"

Invalid branch names:

• "fix/resolve-race-condition"
• "features/widget"
• "improvements/Increase-logo-size"
• "new stuff"