CI review
When checks fail, Limn reads the logs and says what broke and why.
A red check usually means opening a long log and scrolling for the error. The CI review does that for you. It reads each failing GitHub Actions job's log, picks out the error lines, reads the code, and says why the check failed, how sure it is, and whether this pull request can fix it. It is a run of its own, separate from the code review.
#Where to find it
On the pull request's AI Review tab, in the CI check section. It shows a result only for the pull request's latest commit; an earlier commit's diagnosis is hidden.
ConnectionResetError: [Errno 104] at tests/test_webhooks.py:88
Fix: import Decimal in refunds/amounts.py.
Re-check Fix with AI →
#Run a check
- Open the pull request and choose the AI Review tab.
- In CI check, press Check CI. The status line says Reading the logs, then Reading the code.
- Read each failing check's row. Press Re-check after new commits or new failures.
When you start a code review on a pull request whose checks are red, Limn starts a CI check beside it, so you get both.
#Read the result
Each failing check gets one row:
- The cause, in a sentence, and an explanation you can open.
- A category: Code, Test, Flaky or infra, Config or Unclear.
- Confidence, as a percentage. Limn is told to go above 50% only when the log lines it cites show the cause.
- Whether this pull request can fix it. A failure that is not caused by the change says Not from this change.
- A suggested fix, when there is one, and the file and line it points at.
A chip says when the result is out of date: Pushed since, Changed since (other checks fail now) or Passing now.
When Limn cannot read the failure, it says why instead of guessing:
- The failing checks do not run on GitHub Actions, so there are no logs to read. Such checks are listed only. The exception is SonarCloud: with SonarCloud set up, a failing SonarCloud check is explained from SonarCloud's own analysis of the commit, its quality gate and issues.
- The failing jobs’ logs could not be read.
- Nothing is failing on this commit any more.
#Fix it
When at least one failure can be fixed in this pull request, Fix with AI opens the AI Fix tab with just those failures ticked. Nothing changes until you press Start fix, and nothing is pushed until you press Push. This works even when the pull request has no AI review yet. See Choose what to fix.
To read the log yourself, see CI logs.
#When it runs by itself
With auto review on for the workspace, a check that fails on a pull request a person opened is looked at on its own, once for each set of failing checks on a commit. Only failures seen after auto review was switched on are checked. Automatic CI checks have their own daily limit, 20 per workspace by default, and ask your spend budget first. Checks you start never count.