slop/non-conventional-commits
Commit subjects follow Conventional Commits
| Severity | info |
| Tiers | all |
| Stacks | any |
| Scope | root |
| Kind | expr |
| Source | library v0.0.0-20261011205826-ecb4e9b3ffd4 |
| Selected by | fleetlint-slop@0.1.0 |
Requirement
Commit subjects in the recent history (params.commits, default 200) have the form type(scope): subject; merge commits are exempt.
Why
The changelog and the next version number are computed from the subjects.
Applies when
repo.has_gitCheck
For each item in:
commits(params.commits)item.subject.matches(r'^(feat|fix|refactor|perf|test|docs|build|chore|revert|ci|style)(\([^)]+\))?!?: ') || item.subject.startsWith("Merge ")Parameters
commits:200
Fix
Install the commit-msg hook so new commits are checked.
Agent instruction: Use Conventional Commits for new commits. Do not rewrite pushed history without the user’s decision.
See: https://fleetlint.org/baseline/#slop
Generated by fleetlint docs from catalog v0.0.0-20261011205826-ecb4e9b3ffd4.