Branch name validation and conventions for team-scale repositories.
Consistent branch names support navigation, search, and automation. Studio validates names against a git-safe ruleset at creation.
Validation rules
- Initial character: letter or digit
- Allowed: letters, digits,
_,.,/,- - Forbidden:
..; trailing/or. - Maximum length: 100 characters
| Name | Valid | Reason |
|---|---|---|
main | Yes | Default |
feature/billing-overage | Yes | Namespace separator |
release/2026.05 | Yes | Version segment |
/feature | No | Leading / |
feature..x | No | .. |
wip/ | No | Trailing / |
Validation errors appear in the create dialog — correct the name and retry.
Naming conventions
feature/ capability workfix/ defect or regressionspike/ time-boxed investigationrelease/ release preparation
Team policy
Default branch policy
main holds reviewed, deployable state only.
Branch granularity
One branch per feature, fix, or spike — bounded diff scope.
Commit messages
State what changed; reviewers rely on History on the Changes page.
Promotion and archive
Set as default after approval; archive feature branch in the same cycle.
Short-lived Standard branches from current main keep diffs small and merges clean.
Collab rooms stay in Studio and are never matched by Git branch patterns.
See Merge in
Studio.
Last updated on