Skip to content

refresh - #3528

Closed
mlim1972 wants to merge 0 commit into
kunchenguid:mainfrom
mlim1972:main
Closed

refresh#3528
mlim1972 wants to merge 0 commit into
kunchenguid:mainfrom
mlim1972:main

Conversation

@mlim1972

@mlim1972 mlim1972 commented Sep 2, 2026

Copy link
Copy Markdown

No description provided.

@greptile-apps

greptile-apps Bot commented Sep 2, 2026

Copy link
Copy Markdown

Confidence Score: 4/5

The 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

Comment thread bin/fm-pr-poll.sh Outdated
Comment on lines +78 to +79
[ "$review" = CHANGES_REQUESTED ] && [ -n "$head" ] \
&& printf 'changes_requested\t%s\n' "$head"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Review wakes repeat per head

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant