| name | branches |
| description | Create and name git branches following project conventions. Use when creating branches, checking out new branches, or the user mentions branch naming. |
Branch Naming Conventions
Use lowercase kebab-case with type prefix and issue/ticket identifier.
feature/RI-123/add-user-profile
bugfix/RI-789/memory-leak
fe/feature/RI-567/add-dark-mode
be/bugfix/RI-345/fix-redis-connection
docs/RI-333/update-docs
test/RI-444/add-unit-tests
e2e/RI-555/add-integration-tests
feature/123/add-export-feature
bugfix/789/fix-connection-timeout
release/v2.0.0
ric/RI-666/custom-prefix
Branch Types
feature/ - New features and refactoring (affects multiple areas)bugfix/ - Bug fixes (affects multiple areas)fe/feature/ - Frontend-only features (only redisinsight/ui/ folder)fe/bugfix/ - Frontend-only bug fixes (only redisinsight/ui/ folder)be/feature/ - Backend-only features (only redisinsight/api/ folder)be/bugfix/ - Backend-only bug fixes (only redisinsight/api/ folder)docs/ - Documentation changestest/ - Test-related changese2e/ - End-to-end test changesrelease/ - Release branchesric/ - Custom prefix for special cases
Note: When a bug fix affects only the redisinsight/ui/ folder, use fe/bugfix/ prefix instead of bugfix/.
Issue References
- Internal:
RI-XXX (JIRA ticket)
- Open Source:
XXX (GitHub issue number)
- Use
# only in commit messages, not branch names
