Skip to main content
Version: 2.0 (deprecated)

lint

pants lint [args]

Run all linters and/or formatters in check mode.

Backend: ``

Config section: [lint]

Basic options​

None

Advanced options​

per_file_caching​

--[no-]lint-per-file-caching
PANTS_LINT_PER_FILE_CACHING
pants.toml
[lint]
per_file_caching = <bool>
default: False

Rather than linting all files in a single batch, lint each file as a separate process. Why do this? You'll get many more cache hits. Why not do this? Linters both have substantial startup overhead and are cheap to add one additional file to the run. On a cold cache, it is much faster to use --no-per-file-caching. We only recommend using --per-file-caching if you are using a remote cache or if you have benchmarked that this option will be faster than --no-per-file-caching for your use case.

reports_dir​

--lint-reports-dir=<DIR>
PANTS_LINT_REPORTS_DIR
pants.toml
[lint]
reports_dir = <DIR>
default: None

Specifying a directory causes linters that support writing report files to write into this directory.

Deprecated options​

per_target_caching​

--[no-]lint-per-target-caching
PANTS_LINT_PER_TARGET_CACHING
pants.toml
[lint]
per_target_caching = <bool>
default: False
Deprecated, will be removed in version: 2.1.0.dev0.
Use the renamed `--per-file-caching` option instead. If this option is set, Pants will now run per every file, rather than per target.

See --per-file-caching.