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

repo/dev-environment

The development tools are reproducible

Severitywarning
Tiers1, 2
Stacksany
Scoperoot
Kindoutcome
Sourcelibrary v0.8.0
Selected byfleetlint-recommended@v0.8.0

Requirement

Someone with a fresh machine gets the same toolchain and tools as everyone else from what is in the repository: a dev container (.devcontainer/devcontainer.json), a Nix environment with its lock file (a flake with flake.lock, devenv with devenv.lock, devbox with devbox.lock, or shell.nix), a version manager file (mise.toml, .tool-versions), or a tools target that installs pinned versions. Any one of them is enough; the task runner stays the interface that hooks and CI use. facts.container selects the mechanism: devcontainer (the default when a devcontainer.json exists) needs the dev container, docker or podman a task runner that runs its targets in an image, and none one of the others.

Why

Lint and test results that depend on which linter version a contributor happens to have are not results; a second contributor’s first hour should not go into guessing tools.

Fix

Choose. For a container set facts.container to devcontainer, docker or podman and run fleetlint fix --apply: the task runner file and check workflow it writes run inside it (and for devcontainer it writes the container). To stay on the machine, give the tools target pinned versions, add a version-manager file, or commit the lock file of a Nix flake, devenv or devbox environment.

Agent instruction: Ask which mechanism the user wants. Container: set facts.container (devcontainer, docker or podman) in .fleetlint.yaml and run fleetlint fix --apply. Machine: add a tools target to the task runner that installs every tool at a fixed version. Do not add more than one mechanism.

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

A finding that names no file points at .devcontainer/devcontainer.json.

Sources


Generated by fleetlint docs from catalog v0.8.0.