refresh - #3528
Conversation
Confidence Score: 4/5The PR should not merge until unchanged changes-requested PR heads stop generating repeated follow-up work. The persistent GitHub poll emits the same changes-requested result every interval, and the watcher appends each result as a fresh durable wake, allowing duplicate workers to be dispatched against one unchanged PR branch. Files Needing Attention: bin/fm-pr-poll.sh, bin/fm-watch.sh Reviews (1): Last reviewed commit: "fix(bin): sync 14 upstream commits into ..." | Re-trigger Greptile |
| [ "$review" = CHANGES_REQUESTED ] && [ -n "$head" ] \ | ||
| && printf 'changes_requested\t%s\n' "$head" |
There was a problem hiding this comment.
When a pull request remains at the same head with changes requested after the first wake is handled, this poll emits the same result again on every interval and the watcher appends each result as a new wake, causing duplicate follow-up tasks and workers to target the same PR branch.
Context Used: If there is a VISION.md file at the root of the re... (source)
Knowledge Base Used: Change review and merge
No description provided.