| name | commit-conventions |
| description | Commit message style and structure for this repository. |
Commit Message Conventions
Format
Use the following format:
<type>(<optional scope>): <short summary>
Examples:
feat(auth): add MFA to login flowfix(api): handle null payloads in /v2/orderschore(ci): speed up test pipeline
Types
feat– new user-facing featurefix– bug fixrefactor– structural code changes without behavior changechore– tooling, CI, non-runtime codedocs– documentation-only changesperf– performance improvementstest– adding or adjusting tests
Body
- Use when additional explanation is necessary.
- Include:
- Motivation for the change
- Notable design decisions
- Links to tickets or issues
Footer
- Include breaking change notes:
BREAKING CHANGE: [description]
- Include issue references:
Fixes #1234