-
Notifications
You must be signed in to change notification settings - Fork 5.5k
CI: Surface Rust warnings on PRs that touch any Rust code #14173
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
Conversation
fabf5f8
to
68ba824
Compare
Since we're clean on warnings on |
Rust PRs will have a failed CI step if they trigger any warnings. This helps us stay on top of warnings from new Rust releases and also ones we accidentally write. Fix a typo for demo, since this only runs when Rust files are changed.
68ba824
to
27df91c
Compare
❌ Tests Failed✖️no tests failed ✔️62276 tests passed(2 flakes) |
- name: Rust warnings | ||
run: | | ||
set -euo pipefail | ||
cargo check --quiet --all-features --message-format=json \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder if there's a way to extract not only warnings but also errors with jq. It just silently fails right now.

https://github.com/ruby/ruby/actions/runs/16994039992/job/48180380659
Idea is, if you create PRs touching Rust code often, you probably don't
mind being shown new warnings introduced in new Rust releases. They've
been trivial to fix and this will help us stay on top of them.
Closes Shopify#693