You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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 tocargo 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?
The text was updated successfully, but these errors were encountered: