clippy.toml seems to be limited to a select set of configurable lints. I'd like to allow/warn/deny lints based on best practice at my company as a default that developer could override if they have good cause to ignore Clippy. I'd strongly like to avoid adding a header that gets copied and pasted across every project, but all that leaves that I'm aware of is CLI configuration. Running a custom
cargo clippy command in CI/CD isn't quite good enough either. I'd like developers to be able to see the lints as-configured by the Rust guild within my organization.
Is there a way to do this that doesn't involve hacking up
Clippy to take a configuration file of defaults in the home directory? I've been googling around extensively for this and I'm starting to lose it a bit as I recall linting tools in other languages having config files that could live in the project directory or somewhere that applies globally.