fleetlint Policy for a fleet of repositories
v0.11 (latest)
Getting started

lint/configured

A linter is configured

A capability: each stack checks it with its own tools, and every implementation that runs must pass. Implemented for cpp, dotnet, flutter, go, hugo, java, kotlin, node, php, python, ruby, rust.

Severitywarning
Tiers1, 2
Stacksany
Scopeeach
Kindcapability
Sourcelibrary v0.8.0
Selected byfleetlint-recommended@v0.8.0

Requirement

Every stack has a linter beyond the compiler, configured in the repository. A configuration in a parent directory counts for the projects below it when the tool reads it from there.

Why

Without a committed configuration every developer’s editor runs different checks and the build runs none.

Fix

Configure the stack’s linter as described in the stack profile (https://fleetlint.org/stacks/).

Agent instruction: Configure the stack’s linter from the stack profile and run it from the lint target; fix what it reports instead of disabling checks.

Sources


Generated by fleetlint docs from catalog v0.8.0.