Skip to content

Cargo Clippy CI Optimizations #308

@SupremoUGH

Description

@SupremoUGH

In our CI, we run
cargo hack clippy --workspace --feature-powerset --depth 3
and then
cargo hack clippy --workspace --feature-powerset --depth 3 --bins.
However,
cargo hack clippy --workspace --feature-powerset --depth 3 checks both the libraries and the binaries. I propose changing the CI to
cargo hack clippy --workspace --feature-powerset --depth 3 --lib
and
cargo hack clippy --workspace --feature-powerset --depth 3 --bins.

Also, we run
cargo hack clippy --workspace --feature-powerset --depth 3 --examples
which is a no-op because we don't have any. Why don't we remove it until it makes sense?

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-ciArea: Continuous Integration

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions