Commit Guidelines
Commit Message Format
Write clear, descriptive commit messages:
[Type] Brief description
Optional detailed explanation if needed
Types:
feat: New featurefix: Bug fixrefactor: Code refactoringdocs: Documentation changesstyle: Code style changes (formatting, etc.)test: Adding or updating testschore: Maintenance tasks
Examples:
feat: Add campaign creation form
fix: Resolve signature validation error in Step 4
refactor: Optimize table data fetching hook
docs: Update deployment documentation
Commit Best Practices
- ✅ Commit often with logical, related changes
- ✅ Write clear messages that explain what and why
- ✅ Keep commits focused on a single change
- ✅ Don't commit
.envfiles,node_modules, or build artifacts