Lint πŸ”ΒΆ

You MUST use these linting and quality tools where applicable:

Repository Lint Rules πŸ“ΒΆ

You MUST apply these repo-wide rules when you add, move, or review files:

  • Keep broad folders shallow when that helps readability. Direct children SHOULD stay at 12 or fewer items per folder.

  • Treat structural hubs such as roles/, cli/, tests/unit/python/plugins/filter, tests/unit/python/roles, inventories/bundles/servers, inventories/bundles/workstations, plugins/filter, plugins/lookup, group_vars/all, and .github/workflows as intentional exceptions when they are used to organize the tree.

  • You SHOULD prefer smaller, more focused folders over dumping many unrelated files into one directory.

For refactoring guidance, see Refactoring.

Suppression Comments 🚫¢

Lint and external checks share a single per-item suppression syntax based on # noqa / # nocheck markers. The full grammar, position semantics, and the catalog of rule keys live at suppression.md.

Running Specific Lint Tests πŸƒΒΆ

Use INFINITO_TEST_PATTERN to scope the lint test run to a single file:

# Run lint tests for a specific file
make test-lint INFINITO_TEST_PATTERN=test_my_role.py