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

lint/strict

The linter’s required checks are on

A capability: each stack checks it with its own tools. Implemented for cpp, dotnet, go, java, kotlin, python, ruby, rust.

Combine: all. Every implementation that runs must pass: each stack in the repository meets the requirement with its own tools.

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

Requirement

The linter configuration enables the checks the stack profile requires; each missing one is reported.

Why

A linter with its defaults reports style; the checks that find swallowed errors, crashes and oversized functions are mostly off until they are switched on.

Fix

Enable the reported checks in the linter configuration (see https://fleetlint.org/stacks/).

Agent instruction: Enable each reported check in the linter configuration and fix or ratchet the findings it produces instead of suppressing them.

See: https://fleetlint.org/baseline/#static-analysis


Generated by fleetlint docs from catalog v0.2.0.