Re-runs and continuity

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.

Findings remain anchored to the commit Angada reviewed, while matching outcomes carry forward.

Requesting a re-run

A user with write access can request a manual re-run when the pull request is eligible. Manual re-runs bypass the 150-file automatic-review ceiling, but they still follow the Workspace and pull-request rolling caps. 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

• Understand a review — see how findings, evidence, and verdicts fit together.
• Limits and caps — learn which conditions skip a review.