Automations fire on a failed check or an issue
Two more triggers for automations. Check failed fires when a GitHub Actions workflow run, or any other CI's check, ends in failure, and the agent gets the failed job's log around the first error (or the check's own output) along with the failing commit; filter by workflow or check name, branch, and whether only pull requests count. Issue fires when an issue is opened or labeled, with the issue's title and text as the run's context; filter by label, title and author. A comment goes on the pull request or the issue the run is about.
The Triage failed Actions and Fix CI failures recipes now start from the check-failure trigger with the log in hand, and Issue labeled for the agent from the issue trigger. A GitHub Actions failure fires once, through its workflow run. A team's own white-label GitHub App made before today approves the updated permissions (Actions read, and the new events) in its settings on GitHub before these triggers reach it.
More in Triggers.