Let red CI fix itself.

A failed check becomes a fix commit on the same branch. ProPR posts the failure on the pull request, an agent fixes it, and you come back to green checks and one more commit to review.

Describe

Run isolated

Review in GitHub

You start with: A repository with CI on its pull requests
You use: Auto CI follow-up · PR comments
Takes: No action from you; on #2628 the fix landed within four minutes of the failure
Real run: propr #2628

Turn it on for the repository

Switch on automatic CI follow-up in the repository settings. The follow-up docs cover the settings.

Auto CI follow-up switched on for storefront-web: when a GitHub Actions run fails, ProPR sends a corrective task

A check fails

ProPR posts the failure on the pull request: the check, the commit, a link to the run and the failure evidence from the check's output.

The fix lands on the same branch

An agent reads the failure with the PR's context, ProPR pushes the fix to the same branch, and the completion comment explains what changed. Your checks run again on the new commit. The guide to fixing failing CI runs with an AI agent covers the settings and the evidence each fix carries.

Or paste the failure yourself

Copy the failing output into a PR comment. The fix lands the same way, as a follow-up commit.

@maintainercommented on this pull request

The lint check fails: src/checkout/summary.ts exceeds the 400-line max-lines limit. Split the formatting helpers out without changing behavior.

A real red check, fixed.

On public propr #2628, the Validate Changes check failed on a lint rule. ProPR posted the failure at 13:05 UTC; GPT-6 Astra brought VibeAgent.ts under the 400-line limit, and ProPR pushed fix commit 9296e95 at 13:08.

Red check to green commit.Public propr #2628, shortened to the relevant parts: the failing check on 73029d8, ProPR's failure comment, GPT-6 Astra's fix commit 9296e95, and GitHub's check list for it.