The repository currently produces a substantial number of warnings and errors when running:
cargo clippy --workspace --all-targets --all-features
Before Clippy can be enabled as a required pull-request check, the existing findings should be reviewed and resolved or explicitly allowed where appropriate.
Once the workspace reaches a clean baseline, add a dedicated GitHub Actions workflow that runs Clippy independently from build, test, formatting, and documentation checks.
Clippy is specifically a linting tool for finding common mistakes and improving Rust code, but enforcing it only makes sense after the repository has a clean baseline.
The repository currently produces a substantial number of warnings and errors when running:
Before Clippy can be enabled as a required pull-request check, the existing findings should be reviewed and resolved or explicitly allowed where appropriate.
Once the workspace reaches a clean baseline, add a dedicated GitHub Actions workflow that runs Clippy independently from build, test, formatting, and documentation checks.
Clippy is specifically a linting tool for finding common mistakes and improving Rust code, but enforcing it only makes sense after the repository has a clean baseline.