switch to `build.warnings` in CI
Open
Beginner friendly
Nobody has claimed this yet.
easy
github-actions
- Dominant language
- Rust
- Stars
- 16.2k
- Forks
- 1k
- Avg merge
- 2d 6h
- Merged PRs (30d)
- 66
Description
We use -D warnings in a couple of places
We can use https://doc.rust-lang.org/cargo/reference/unstable.html#warnings instead.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Search the CI configuration for the places that pass -D warnings, then read Cargo's unstable build.warnings documentation linked in the issue. Update those CI settings to use the supported configuration and confirm the CI checks still enforce warnings as errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, ci-cd
- Issue type
- Refactor
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100