Orchestrator should detect REQUEST_CHANGES from reviewer

t-318·WorkTask·
·
·
·Omni/Agent/Telegram/Orchestrator.hs
Created4 months ago·Updated4 months ago·pipeline runs →

Description

Edit

The orchestrator treats exit 0 from pi-review.sh as approval and gets the HEAD commit hash. But REQUEST_CHANGES also exits 0 (it just adds feedback without committing). The orchestrator should either: 1. Check if there's actually a new commit (compare before/after HEAD) 2. Or pi-review.sh should exit with a distinct code for REQUEST_CHANGES (e.g. exit 2)

Current behavior: orchestrator marks task done even when reviewer requested changes.

Git Commits

949727f9Fix orchestrator REQUEST_CHANGES detection (t-318)
Ben Sima4 months ago2 files

Timeline (2)

🔄[human]Open → InProgress4 months ago
🔄[human]InProgress → Done4 months ago