Git Workflow Standards
Branch Naming
code
feature/<task-id>-<short-description> fix/<issue-id>-<short-description> refactor/<scope>-<description> docs/<scope>-<description>
Commit Message Format
code
<type>(<scope>): <subject> <body> <footer>
Types
- •
feat: New feature - •
fix: Bug fix - •
docs: Documentation - •
style: Formatting - •
refactor: Code restructuring - •
test: Adding tests - •
chore: Maintenance
Example
code
feat(auth): add JWT token validation Implement JWT validation middleware for protected routes. Closes #123
Pull Request Guidelines
PR Title
code
feat(scope): short description
PR Description
markdown
## Summary Brief description of changes. ## Changes - Change 1 - Change 2 ## Testing How this was tested. ## Checklist - [ ] Tests pass - [ ] Lint passes - [ ] Documentation updated
Workflow Steps
- •Create feature branch from main
- •Make commits following conventions
- •Run quality checks before push
- •Create PR with description
- •Address review feedback
- •Squash and merge