All updates

Code Reviews Now Reliably Start And Report Back

A round of fixes closes several ways a pull request could slip through without a real review, so every reviewed task now gets an honest verdict.

Summary

A pull request on a project with an assigned reviewer agent could, in a handful of situations, slip through without ever receiving a real review — reviewed against the wrong task, skipped because of an unrelated earlier run, or stuck with no verdict recorded at all. A set of fixes closes each of those gaps, so reviews now reliably start, run against the right work, and report back.

What You Gain

Previously, a few specific situations could leave a pull request effectively unreviewed even though a Review agent was assigned to the project: a pull request could be checked against a different, related task instead of its own; a reviewer could be skipped because it had reviewed an earlier version of the same work; picking a reviewer on a task didn't always start the review right away; and a review that silently failed to finish could leave its pull request waiting indefinitely with no verdict ever recorded. Each of those meant code could end up merged, or sitting unreviewed, without anyone noticing.

Now each of those paths is closed: a pull request's review applies only to its own task, a reviewer is no longer disqualified by unrelated past activity, choosing a reviewer starts the review immediately, and a review with no verdict is retried and then clearly flagged. Pull requests already stuck this way were cleared too.

How It Works

  • A pull request's review now applies to its own task only, even when its description happens to mention other related tasks.
  • A reviewer is no longer unfairly disqualified by activity that isn't actually its own earlier review of the same work.
  • Assigning a reviewer starts the review immediately, rather than waiting for the next change to the code.
  • A review that doesn't produce a verdict is retried, then flagged for you instead of sitting pending with no sign anything is wrong.
  • Every failed or stuck review is now recorded on the task's own activity history, so you can see exactly what happened and when.

Where to Find It

This applies automatically to every project with an assigned Review agent — there's nothing to configure. The latest desktop app or CLI is recommended to get the full benefit.

See what else shipped that month on the Effigate Command Center changelog, or try Effigate Command Center with your own team.

D
Shipped by Dev Team
Palzin LLC
What did you think of this update?
Every reaction gets seen by the team.