Feature Branch Naming Convention

Feature Branch Naming

Feature branches are the most common branch type in any git workflow. They represent new functionality being added to the codebase and typically originate from the develop or main branch.

Standard Format

feature/{ticket}-{description}

Examples

Input	Generated Branch Name
PROJ-1234 + "Add user authentication"	feature/proj-1234-add-user-authentication
#567 + "Implement dark mode toggle"	feature/567-implement-dark-mode-toggle
ENG-89 + "API rate limiting"	feature/eng-89-api-rate-limiting

Why Feature Prefixes Matter

Using the feature/ prefix serves multiple purposes in a development workflow:

1. Visual organization — When listing branches with git branch, feature branches are grouped together alphabetically, making it easy to scan active work.
2. CI/CD integration — Many CI systems (GitHub Actions, GitLab CI, Jenkins) can trigger specific pipelines based on branch name patterns. A feature/* pattern ensures feature branches run the correct build and test suite.
3. Code review context — Reviewers immediately understand the branch's purpose from its name, reducing the need to read the PR description before starting review.
4. Branch protection rules — Git hosting platforms let you configure rules like "require pull request reviews for branches matching feature/*", enforcing quality gates.

Tips for Good Feature Branch Names

• Keep the description to 3-5 words that capture the core change
• Use the ticket number from your project tracker for traceability
• Avoid generic names like feature/update or feature/changes
• Include the domain area when helpful: feature/PROJ-123-auth-oauth-google