Add a setup-commands input to the cargo mutation workflow#326
Conversation
Callers cannot inject steps into a `workflow_call` job, so repositories whose builds need job-level preparation had no way to satisfy it before cargo-mutants runs. The concrete case is agent-template-rust review feedback: generated repos render `.cargo/config.toml` with `-fuse-ld=mold` on the default Linux target and their CI installs mold before any cargo command; the mutation baseline would fail to link on a bare runner. `setup-commands` (default empty, preserving existing behaviour) runs caller-supplied shell in each mutants job after toolchain setup and before cargo-mutants, via a temp script under `set -euo pipefail`. The input executes with the same privileges the caller's own workflows already hold in their repository.
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 21 minutes Your organization has reached its usage spending cap. Adjust your spending cap in the billing tab. 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: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Summary
Callers cannot inject steps into a
workflow_calljob, so repositories whose builds need job-level preparation (linkers, system packages) had no way to satisfy it before cargo-mutants runs. The concrete case is review feedback on agent-template-rust#52: generated repos render.cargo/config.tomlwith-fuse-ld=moldand their CI installs mold before any cargo command — the mutation baseline would fail to link on a bare runner.This branch adds a
setup-commandsinput (default empty) to .github/workflows/mutation-cargo.yml, executed in each mutants job after toolchain setup via a temp script underset -euo pipefail, and documents it in the caller guide. The commands run with the same privileges the caller's own workflows already hold.Validation
actionlint,zizmor: cleanmake markdownlint: 0 errors