Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: Use auguwu/clippy-action@1.4.0 to run clippy #339

Conversation

Techcable
Copy link
Member

@Techcable Techcable commented Sep 23, 2024

Makes clippy warnings trigger warnings instead of hard errors,
fixing issue #338

HACK: Use my fork of auguwu/clippy-action to support "features" input.

Split off from PR #337 , which is logically independent.

A couple issues:

The --features flag isn't working when used with check-args
We get lots of duplicate warnings by running multiple feature combinations

IDEA: Maybe run just once with --all-features?

Make sure to:

  • Add an entry to CHANGELOG.md (if necessary)

Makes clippy warnings trigger warnings instead of hard errors,
fixing issue slog-rs#338

HACK: Use my fork of auguwu/clippy-action to support "features" input.
@Techcable
Copy link
Member Author

I decided we want build failures on warnings, as discussed in #338

We only trigger build failures on warnings on the "hardcoded recent stable," so clippy changes shouldn't unexpectedly fail the build.

@Techcable Techcable closed this Sep 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant