fleetlint Policy for a fleet of repositories
v0.10
Getting started

slop/vague-commit-messages

Commit subjects say what changed

Severityinfo
Tiersall
Stacksany
Scoperoot
Kindexpr
Sourcelibrary v0.7.0
Selected byfleetlint-slop@v0.7.0

Requirement

No commit in the recent history (params.commits, default 200) has a description that is only fix, update, wip, changes, misc or cleanup, with or without a Conventional Commits type (fix: update is as vague as update).

Why

The history is the record of why the code changed; a one-word subject records nothing.

Applies when

repo.has_git

Check

For each item in:

commits(params.commits)
!item.subject.matches(r'(?i)^(\w+(\([^)]*\))?!?:\s*)?(fix(es)?|update[sd]?|wip|changes?|misc|stuff|tmp|test|minor|cleanup|\.)\.?$')

Parameters

  • commits: 200

Fix

Write the subject from the diff; squash work-in-progress commits before merging.

Agent instruction: Write subjects from the diff. Do not rewrite pushed history without the user’s decision.

Sources


Generated by fleetlint docs from catalog v0.7.0.