Connect GitHub Actions with Unblocked to analyze CI failures

GitHub Actions adds runtime evidence to the code and pull-request history Unblocked already understands. When a selected workflow fails, the CI Failure Agent uses the failure output and repository context to identify a likely cause and reports only when its confidence is high.

Because Unblocked already understands your codebase, pull requests, and team discussions, its analysis is grounded in that context — it explains what broke and suggests a fix, with links back to the relevant code and history.

Reports are posted as a comment on the pull request and are gated by confidence, so the agent stays quiet unless it has something useful to say. Each developer can turn reports on or off for their own PRs in personal settings.

What you get

• Automatic failure analysis — The CI Failure Agent reads failed GitHub Actions runs and analyzes the logs to find the root cause — no manual log-digging.
• Root-cause reports on the PR — When confident, Unblocked posts a comment on the pull request explaining the failure and suggesting a fix.
• Grounded in your codebase — Analysis draws on your indexed code, pull requests, and discussions, so suggestions fit how your project actually works.
• Confidence-gated, per-developer control — Reports post only when Unblocked is highly confident, and each developer can toggle them for their own PRs in Personal Settings → Preferences.

Need screenshots or troubleshooting?This is a concise connection summary. Follow the complete setup guide ↗

Prerequisites

• An Unblocked account (free to start).
• Your source code connected to Unblocked — the CI Failure Agent runs on your connected repositories.
• Permission to grant Unblocked access to GitHub Actions for the selected repositories.

Connect GitHub Actions to Unblocked

1. In Unblocked, open Settings → Continuous Integration and click Add a CI Provider.
2. Click the GitHub Actions tile, and accept any additional GitHub permissions if prompted.
3. Click Select Repositories and toggle the repositories where you want the CI Failure Agent enabled.
4. Click Save Settings — Unblocked will analyze CI failures in those repositories and post reports to pull requests.

Examples of GitHub Actions failures the CI Failure Agent can investigate:

• Why did the GitHub Actions build fail on this pull request?
• What is the root cause of the failing test in CI?
• Which recent change most likely caused the CI failure?