Fixed A Review-And-Merge Loop On Already-Reviewed Code

Summary

A particular sequence of events could cause the same piece of already-merged code to be reviewed, approved, and merged again and again on a loop — in one case dozens of times for a single commit. That loop is now closed: a commit that's already been reviewed and merged for a task is recognized as such and left alone.

What You Gain

This kind of loop wasted review capacity on work that was already finished and merged, and created noisy, repetitive activity on the affected task that had nothing useful to show for it. It happened because the system occasionally recognized "already reviewed" by looking at the pull request itself rather than the actual commit inside it — so a new pull request opened for a commit that had already been reviewed and merged would be treated as brand new, when it should have been recognized immediately.

Now the check looks at the commit directly, so a pull request can't trigger a repeat review or a repeat auto-merge of something that's already done. A genuinely new commit is still always reviewed as expected — only an exact repeat is skipped.

How It Works

• A review no longer starts for a pull request whose exact commit has already received a verdict elsewhere on the same task.
• Auto-merge no longer merges a pull request whose commit was already merged for the same task; it's left open with a note explaining that it duplicates already-merged work.
• A genuinely new commit is always reviewed as normal — this only skips an exact repeat, never a real change.
• The task's own activity history explains when and why a review or merge was skipped, so nothing happens invisibly.

Where to Find It

This applies automatically to every project using agent-driven review and auto-merge — there's nothing to configure.

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