GitHub Actions

Your CI is the source of truth.

RepoWarden reads your GitHub Actions check results, pulls failing logs, and uses them to fix the PR. No extra runners to configure, no YAML to learn — whatever you run on every push is what RepoWarden trusts.

Sign in with SSO →
01What it reads

From your existing checks

Check suite results

When a check suite completes, RepoWarden picks up whether each job passed or failed and which ones gate merging.

Failing job logs

On failure, RepoWarden fetches the raw logs and annotations, pipes them to an LLM alongside the diff, and fixes the actual error — not just the symptom.

Required checks

RepoWarden respects branch protection. If a required check fails, the PR stays open until it passes. No sneaky force-merges.

02Zero config

What you don't have to do

Explicitly not required. RepoWarden works with whatever your repo already runs.

Add a repowarden.yml workflow
Configure self-hosted runners
Re-write your existing CI
Grant extra secrets or tokens
Set up a separate build environment
Learn a new DSL
03Fix loop

When CI fails, RepoWarden fixes it

No rebase comments, no manual re-runs. This sequence runs automatically when a RepoWarden PR fails its checks.

  1. 1check_suite webhook fires with a failure status
  2. 2RepoWarden fetches the failing job's annotations and log tail
  3. 3The diff, log, and changelog for any upgraded packages go to Claude
  4. 4A fix is written, tests rerun locally in a sandbox, and the PR is force-pushed
  5. 5CI reruns; if it passes, the PR is ready. If it fails again, RepoWarden bisects which dep caused it
Get started

Works with your CI, on day one

No extra workflow files. Just install the GitHub App.

Morty Proxy This is a proxified and sanitized view of the page, visit original site.