ci(build): replace full builds with cargo check#76
Conversation
- Replace `cargo build --all` (debug) + `cargo build --all --release` with `cargo check --all --all-targets` - cargo check only does type-checking without producing binaries, ~4x faster while still catching compilation errors and warnings - Release builds should only happen in release workflow, not PR CI - Remove unnecessary rustfmt/clippy components from build job (those are installed in the lint workflow)
|
Warning Rate limit exceeded
Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 7 minutes and 39 seconds. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
Changes merged into PR #71 |
1 participant
Summary
cargo build --all(debug) +cargo build --all --releasewithcargo check --all --all-targetsrustfmt, clippycomponents from the build jobWhy
The Build job was doing two full compilations:
cargo checkonly does type-checking without producing binaries. It:-D warningsviolationsRelease builds belong in the release workflow only, not PR CI. If
cargo checkpasses and tests pass, the code is correct.Expected impact
Related
PR #71 (mold linker) will further speed up test/lint jobs once merged.