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

changelog/generator-configured

Changelog generation is configured

Severityinfo
Tiers1
Stacksany
Scoperoot
Kindoutcome
Sourcelibrary v0.6.0
Selected byfleetlint-recommended@v0.6.0

Requirement

The changelog is generated from the commit history, then edited: a stack-neutral generator (git-cliff in cliff.toml, .cliff.toml, [tool.git-cliff] or [workspace.metadata.git-cliff]; GoReleaser, whose changelog is on unless changelog.disable; release-please; cocogitto; semantic-release in .releaserc*, release.config.* or package.json release; commitizen) or the stack’s own (changesets for npm, towncrier for Python), configured in its own file or in the manifest.

Why

Hand-written changelogs drift from the commits; generated ones can be trusted and edited.

Fix

Add cliff.toml; fleetlint fix --apply writes the template.

Agent instruction: Add cliff.toml for git-cliff with Conventional Commits groups; fleetlint fix --apply writes the template.

fleetlint fix can apply this rule’s fix automatically (1 action(s)).

A finding of this rule points at cliff.toml.

Sources


Generated by fleetlint docs from catalog v0.6.0.