CFR from GitHub Actions

A minimum-viable pipeline: workflow_run event, conclusion field, post-deploy fail tag.

Oliver Wakefield-Smith

Founder, Digital Signet. Built siemcost / monitoringcost / itbudgetcalculator.

Updated 21 Jun 2026

Direct answer

GitHub Actions exposes workflow_run events with a conclusion field of success / failure / cancelled GitHub Actions Events2026. Subscribe via webhook or poll the Workflow Runs REST APIGitHub Workflow Runs API2026 and persist deploy events. Tag retrospective failures via an incident-correlation worker.

Workflow-tag convention

Tag deploy workflows with a label your consumer can filter on (deploy: productionin the workflow metadata, or by name match). Without a tag, you cannot tell deploys apart from CI runs.

Retroactive failure tagging

The conclusion field tells you if the deploy job itself failed. It does not tell you if the deploy succeeded but caused a production incident. Pair a 60-minute incident-correlation window: if an incident fires within 60 minutes of a successful deploy, tag the deploy as failed.