2 min lesson

Run CI triage without noisy pull requests

Configure one GitHub CI trigger, write its three decision paths and inspect the first successful and failed runs.

Check your understanding

Complete the practice "Configure GitHub CI triage with a silent success path".

Outcome: The successful run creates no comment or pull request. The failed run either opens one bounded draft pull request or records why it stopped.

Configure GitHub CI triage with a silent success path

Trigger, repository, decision rules, first-run check

SayThe api-ci workflow is stable. I want an agent to inspect completed runs on acme/api, but only a failed run with a safe fix should produce a pull request.

TypeTrigger: Workflow run completed

DoChoose the GitHub Workflow run completed trigger and connect it to acme/api.

SeeThe selected completed-workflow event starts the automation, with acme/api as its codebase.

TypeIf the workflow conclusion is not failure, stop. Do not comment and do not open a pull request.

SeeA successful or cancelled run has an explicit no-action path.

Type

If it failed, inspect the first failing step and logs. Open a draft pull request only for a safe fix inside packages/api and its tests. Otherwise record the cause in the run and stop.

SeeThe prompt separates a bounded code fix from an unclear or infrastructure failure. Pull request creation remains conditional.

DoSave and activate the automation for acme/api. Inspect the first successful run and the first failed run before adding another repository or trigger.

SeeThe successful run creates no comment or pull request. The failed run either opens one bounded draft pull request or records why it stopped.

Learn more

Optional practice

Test yourself on Run CI triage without noisy pull requests

QWhich result proves the CI triage automation is ready to keep?