Git Conventions
| Field | Details |
|---|---|
| Status | Active |
| Last Updated | 05-11-2026 |
Purpose
To maintain a consistent, readable git history with meaningful branch names and commit messages
Scope
Applies to: All repositories under Torcue
Does not apply to: Personal forks, archived projects
Branch Naming
Format
<type>/<ticket-id>-<short-description>
Use kebab-case, lowercase, hyphens to separate words.
Types
| Type | When to Use |
|---|---|
feature/ |
New features |
bugfix/ |
Bug fixes |
hotfix/ |
Urgent production fixes |
release/ |
Release preparation |
chore/ |
Non-code tasks (deps, config) |
Examples
feature/PROJ-123-add-login-page
bugfix/PROJ-456-fix-header-overflow
hotfix/PROJ-789-security-patch
release/v1.2.0
chore/PROJ-321-update-dependencies
Refer to Conventional Branch for full spec.
Commit Messages
Format
<type>(<scope>): <short-description>
Types
| Type | When to Use |
|---|---|
feat |
New feature |
fix |
Bug fix |
docs |
Documentation changes |
style |
Code style (formatting, no logic change) |
refactor |
Code restructuring |
perf |
Performance improvements |
test |
Adding or updating tests |
chore |
Maintenance tasks |
Rules
- Keep description under 72 characters
- Use lowercase, no period at end
- Use imperative mood ("add" not "added")
- Add scope when relevant:
feat(api): add user endpoint
Examples
feat(auth): add Google OAuth login
fix(api): handle empty response from payment service
docs: update API documentation links
refactor: extract validation logic into helper
Refer to Conventional Commits for full spec.
Exceptions
Hotfix commits may use abbreviated descriptions when time is critical, but must follow the format
Related Documents
Changelog
| Version | Date | Author | Change |
|---|---|---|---|
| 1.0.0 | 05-11-2026 | Tibin Sunny | Initial version |