Effigate Now Catches Work That Merged Into an Abandoned Branch

Summary

When two related pieces of agent work are in progress at the same time, it's possible for one to merge into a branch that the other has already abandoned — and until now, Effigate Command Center had no way to notice. It now checks every merge against your repository's actual main branch, and tells you plainly whenever work has landed somewhere that never reaches it, instead of marking the task done.

What You Gain

Previously, a task could be marked complete, show an "approved" notification, and have the right-looking merge notes — all while its actual code changes never reached your main branch at all. This happened when one piece of work built on another that was still in progress, and the one it depended on was merged and then abandoned before the second piece caught up. The system had no way to tell a healthy merge from one that landed on a dead end, so it reported success either way.

Now every merge is checked against your repository's real main branch. A normal merge, or one that lands on another task's branch that's still actively open, is treated as before. But a merge into a branch whose own related work has already finished is flagged immediately: the task is left exactly as it was, with a clear note explaining that its changes are stranded, rather than being silently marked done. The moment a branch is abandoned this way, anything still waiting on it is flagged too, so the problem surfaces right away instead of only after it causes a second, compounding issue.

How It Works

• Every merge is checked against your repository's actual default branch, not just assumed to be correct.
• A task whose pull request merges into an abandoned branch is flagged with an activity note and a notification, instead of being marked done.
• Pull requests tied to an abandoned branch lose their "ready to merge" badge in the task view, replaced with a clear warning to retarget them.
• These warnings also surface in your Decision Queue, so you don't have to stumble onto the affected task to notice.
• A parent task's own work is no longer allowed to merge while any of its related sub-tasks are still unfinished, closing a related ordering issue.

Where to Find It

This protection runs automatically on every project connected through GitHub — there's nothing to configure. You'll see the new warnings directly on a task and in your Decision Queue if this situation ever comes up.

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