Skip to content

Add a setup-commands input to the cargo mutation workflow#326

Merged
leynos merged 1 commit into
mainfrom
add-mutation-setup-commands
Jul 7, 2026
Merged

Add a setup-commands input to the cargo mutation workflow#326
leynos merged 1 commit into
mainfrom
add-mutation-setup-commands

Conversation

@leynos

@leynos leynos commented Jul 7, 2026

Copy link
Copy Markdown
Owner

Summary

Callers cannot inject steps into a workflow_call job, 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.toml with -fuse-ld=mold and their CI installs mold before any cargo command — the mutation baseline would fail to link on a bare runner.

This branch adds a setup-commands input (default empty) to .github/workflows/mutation-cargo.yml, executed in each mutants job after toolchain setup via a temp script under set -euo pipefail, and documents it in the caller guide. The commands run with the same privileges the caller's own workflows already hold.

Validation

  • YAML parse, actionlint, zizmor: clean
  • make markdownlint: 0 errors

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.
@leynos leynos enabled auto-merge (squash) July 7, 2026 10:22

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry @leynos, you have reached your weekly rate limit of 500000 diff characters.

Please try again later or upgrade to continue using Sourcery

@coderabbitai

coderabbitai Bot commented Jul 7, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: e768976c-e768-43aa-832e-61e9a92748bb

📥 Commits

Reviewing files that changed from the base of the PR and between bf19d93 and 96e4fad.

📒 Files selected for processing (2)
  • .github/workflows/mutation-cargo.yml
  • docs/mutation-cargo-workflow.md
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch add-mutation-setup-commands

Comment @coderabbitai help to get the list of available commands.

@leynos leynos merged commit 0c8bd60 into main Jul 7, 2026
27 checks passed
@leynos leynos deleted the add-mutation-setup-commands branch July 7, 2026 10:27
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant