Customization Options
Commit Message Preview
Copy Message
feat(ui): add user profile avatar upload
Implement the ability for users to upload and crop profile avatars
- Add image upload component with drag-and-drop
- Add image cropping functionality
- Handle file size and type validation
- Store images in CDN with user-specific path
feat
ui
Recently Generated Commit Messages
How to Write Good Commit Messages
Effective commit messages are essential for maintaining a clear and useful git history. A well-structured commit message follows these guidelines:
The Conventional Commits Standard
Conventional Commits is a specification for adding human and machine-readable meaning to commit messages. It provides an easy set of rules for creating an explicit commit history.
type(scope): subject
body
footer
- Type: Describes the kind of change (feat, fix, docs, etc.)
- Scope: (Optional) Describes what area of the codebase was affected
- Subject: A concise description of the change
- Body: (Optional) More detailed explanation of the changes
- Footer: (Optional) Information about breaking changes or issue references
Common Commit Types
- feat: New feature or functionality
- fix: Bug fix
- docs: Documentation changes
- style: Code style/formatting changes (not affecting functionality)
- refactor: Code changes that neither fix bugs nor add features
- perf: Performance improvements
- test: Adding or fixing tests
- build: Changes to build system or dependencies
- ci: Changes to CI configuration or scripts
- chore: Regular maintenance tasks
- revert: Revert a previous commit
Best Practices
- Keep the subject line under 50 characters
- Use imperative mood in the subject line (e.g., "Add" instead of "Added")
- Don't end the subject line with a period
- Separate subject from body with a blank line
- Wrap the body at 72 characters
- Use the body to explain what and why, not how
- Reference issues and pull requests in the footer