ci: simplify Nix setup - #147
Conversation
|
Warning Review limit reached
Next review available in: 51 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
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 |
bc643e0 to
1c6b4fb
Compare
Summary
nix-quick-install-actionnix-developseparate.#cishell for test/coverage and.#ci-releasefor release toolingWhy
The latest CI baseline showed the cache post-step taking 73s for stable tests and 56s for MSRV tests. The stable job took 2m13s overall, while its test command took 5s. The release baseline also spent 14s in the cache post-step for a 1s changelog operation.
The focused shells retain only the capabilities each workflow needs: the shared Just shell hook for CI and the x52 release tools for release.
Validation
nix develop .#ci -c just --listnix develop .#ci-release -c command -v x52-bump-changelogsnix develop .#ci-release -c command -v x52-update-release-notesnix flake check --no-build --all-systemsThe release and coverage workflows run only after pushes to
main; the PR CI workflow validates the quick installer path directly.