Back

Triage failed CI runs as they're reported

A likely cause and suggested fix for each failed build your CI sends over

EngineeringWhen CI reports a failed run
Prompt

My CI just reported a failed run to this workflow's webhook. The details it sent, such as the repository, branch, commit, and job or log link, are included above as the run's input. Open the failing job's logs and find the first real error, not the cascade after it. Check whether the same test or step failed recently on other branches, which usually means it's flaky rather than broken by this commit. Write a short triage: the failing step, the error, the likely cause (this commit, a flaky test, or infrastructure), and a suggested fix or the [one or two] files to look at. Don't push anything or re-run the job. If the input doesn't include a way to reach the logs, say what was missing.

Works withgithub.com