Commit shape
<type>(<scope>): <short description>
Use an imperative description that explains the change. Keep the scope meaningful to the repository.
Common types
| Type | Purpose |
|---|---|
| feat | Add a capability |
| fix | Correct behaviour |
| docs | Change documentation |
| refactor | Restructure without changing behaviour |
| test | Add or correct tests |
Example
fix(consumer): commit offset after durable handling
Preserve retry eligibility when persistence fails.
Commit conventions make history easier to scan. They do not replace a useful explanation in the pull request.