CI setup
Wire it into the post stage so it explains failures without ever changing the outcome. Pick your pipeline:
GitLab CI
The .gitlab-ci.yml job, MR notes, an LLM endpoint, and self-hosted instances.
GitHub Actions
The workflow, plus the full action reference: inputs, outputs, PR comments, Enterprise.
Local & air-gapped
Run it from your laptop, ship it as an image, or install from an offline wheel bundle.
The shape is the same everywhere
- Runs only on failure. A post-stage job gated on the pipeline's result, not a step in your build.
- Read-only, and always exits 0. Adding it cannot fail your pipeline or mask the real error.
- Needs one read-scoped token to fetch the failed run's logs — and nothing else.
- The model is optional. Without one you get the deterministic report, not a stub.
What differs between providers is only where the run id comes from and how a note gets posted back. Requirements covers the token scopes; Configuration covers every key you can set from the job.