Skip to main content
When a review completes, Ito posts a summary comment on the pull request listing all tests it ran, and then adds in line comments for each bug or issue it finds. If GitHub comments are turned off for a repository, review results remain available in the Ito dashboard.

​
Review comments

​
Summary comment

The summary comment shows the review result, test counts, findings attributed to the current PR, additional findings that appear pre-existing, and a link to the full Ito results on our site at app.ito.ai.

​
Inline comments

For bugs and issues Ito found that are tied to changed code in the PR, Ito adds an inline comment on the relevant line in the GitHub diff. Use the inline comment to review the finding in context and follow its link to the full evidence in Ito. You can then comment on or resolve the comment to give Ito feedback, or acknowledge a fix of the issue.

​
Dismiss a finding

If your organization has reviewer-dismissal enabled, dismiss an Ito finding in GitHub when you have reviewed it and do not want it reported again. Ito keeps the dismissed finding visible in review history and does not re-report the same finding on later runs.

​
Diff report comments

When incremental review is enabled, follow-up commits on a PR receive a diff report comment instead of a full report. The diff report focuses on what changed since the previous commit and clearly separates tests Ito verified on this commit from tests it carried forward from the prior run.

​
Headline

The diff report headline has two lines so the math is internally consistent:
  • X test cases ran this commit — The verified count, broken down into passed ✅, fixed 🔧, failed ❌, and additional findings ⚠️. These are the tests Ito actually executed against the current commit.
  • ↪️ Carried forward from prior run — Counts of tests that were not retested this commit because Ito judged them unaffected by the diff. Reported separately so they do not inflate the trust signal.
If any tests are no longer applicable (their target code was removed or renamed), a third line summarizes that too.

​
Sections

The diff report groups results into the following collapsible sections:

​
Origin column

The Failures and Additional Findings tables include an Origin column so reviewers can gauge trust without expanding details. Failures are sorted top-down by actionability:
  • 🆕 New — A new test that failed on this commit.
  • 🔁 Regression — A test that passed previously and now fails.
  • 🔻 Still broken (verified) — A failure Ito retested and confirmed on this commit.
  • 🔻 Still broken (inherited) — A failure carried forward from the prior run; not retested this commit.
Additional findings use the same Origin convention with 🆕 New for findings observed this commit and ↪️ Inherited for carry-forward findings.
When triaging a diff report, start at the top of the Failures table. Newly introduced failures and regressions are sorted first; inherited carry-forward entries appear last.

​
Control comment behavior

Open Settings → Automation to choose whether Ito posts results to GitHub for each repository.
  • When Comments is on, Ito posts summary and applicable inline comments on each GitHub PR it runs on.
  • When Comments is off, Ito still runs eligible reviews, but results remain in the Ito dashboard only.
For the full set of review, draft-PR, bot-PR, and comment controls, see Automation Settings.
  • Test Runs — The run that triggers the comment
  • Test Cases — The individual results summarized in the comment
  • Severity Levels — How failures are classified in the comment