AI Review

Re-runs and continuity

What Angada keeps, updates, and skips when a pull request changes.

A new head on a pull request starts a fresh review of the latest code. Angada waits 90 seconds after a push before it starts, so a burst of commits produces one review of the final head instead of several partial reviews.

What stays with the finding

When Angada finds the same issue after a push, it keeps the finding's identity and outcome. A dismissal remains dismissed, and a resolved issue does not return as a new finding merely because its line moved or its file was renamed.

Matching inline comments update in place. Your pull request stays readable instead of accumulating one copy of the same finding for each re-review.

Requesting a re-run

There are three ways to request another review, and each has its own access rule:

  • A member of the Angada workspace roster can post @angada-ai review as a top-level comment in the pull request's Conversation tab. The owner of a personal GitHub installation can also use this mention. See Commands for the full syntax.
  • A workspace admin can request a manual review from Angada's web app or REST API.
  • A GitHub user who is allowed to rerun the check can use Re-run in GitHub Checks.

Each path requires a new, eligible pull-request head. Angada does not start a duplicate review when the current head has already been reviewed; push a new commit first. Manual re-runs bypass the 150-file automatic-review limit, but they still follow the per-pull-request cap and any enabled Workspace cap. If the check says skipped, read Limits and caps before trying again.

When a review changes shape

  • A new commit supersedes an older in-progress review. Angada publishes the current head rather than presenting old work as the current result.
  • A finding that no longer applies disappears from the current review. Its prior commit evidence remains meaningful for the revision where Angada found it.
  • A review that cannot finish does not turn into a clean result. Check the visible status, then use Troubleshoot a review.

Next steps

On this page