Repository navigation
Add Branch Naming Convention Enforcement - #102
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR introduces an automated GitHub Actions workflow that enforces a standardized branch naming convention across the repository to improve organization and consistency.
Changes :
Added branch-naming.yml workflow that triggers on branch creation
Implements automatic validation and deletion of non-compliant branch names
Protects core branches (main, dev, dev-stage, staging, develop) from validation
Branch Naming Convention
All new branches must follow this pattern:
Areas:
fe - Frontend changes
be - Backend changes
infra - Infrastructure/DevOps
config - Configuration changes
Types:
feat - New features :
fix - Bug fixes
hotfix - Critical fixes
docs - Documentation
refactor - Code refactoring
chore - Maintenance tasks
release - Release branches
Examples:
✅ fe/feat/user-dashboard
✅ be/fix/auth-validation
✅ infra/chore/docker-setup
❌ random-branch-name
❌ 86ex9q6zz-feature
Behavior:
New branches: Invalid branch names are automatically deleted
Existing branches: Not affected (workflow only runs on creation)
Protected branches: dev-stage and other core branches are exempt from validation
Impact
⚠️ Team members must use the correct naming format when creating new branches
📋 Improves branch organization and searchability
🔍 Makes it easier to identify branch purpose at a glance
Claude Sonnet 4.5 • 1x