Reviews Stop Looping, Pull Requests Stay on Task
Automatic code reviews now stop retrying after two unresolved attempts, and a task only adopts pull requests from its own project's repository.
Summary
Two reliability fixes tighten up how automatic reviews and GitHub pull requests connect to your tasks. Reviews that keep ending without a clear verdict now stop retrying instead of looping, and a task can no longer mistakenly adopt a pull request from an unrelated repository as its own.
What You Gain
Previously, a commit could be reviewed again and again if each automatic review happened to end without producing a verdict, since the system only recognized a review as "finished" once a verdict was recorded. A commit stuck in that state could trigger review after review with no end in sight. Separately, any pull request that happened to mention a task's identifier — even from an unrelated repository — could become that task's main pull request, get reviewed as if it belonged to the task, and close the task automatically when merged.
Both are now tightened. A commit gets at most two automatic reviews that end without a verdict; after that, no further automatic review starts, and the task's history explains why. You can still start a review yourself at any time, and a new commit resets the count. A pull request only becomes a task's own when it comes from a repository registered to that project; pull requests from anywhere else are shown for reference, but no longer drive reviews or close tasks.
How It Works
- A review cap, not a retry loop. Two unresolved automatic reviews of the same commit is the limit; the task's timeline records that no further review ran and why.
- Manual reviews are unaffected. You can still start a review yourself at any point, regardless of the automatic cap.
- A fresh commit resets the count. Pushing a new commit to the task gives it a clean slate for automatic reviews.
- Pull requests stay scoped to their project. A pull request only counts as a task's own when its repository is registered on that task's project; otherwise it's linked for reference only, with a note in the task's history.
- No change for simple setups. Projects with a single registered repository behave exactly as before.
Where to Find It
Both fixes are live on the server already and need no app update to take effect.
See what else shipped that month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.