Fix review agent duplicate replies by adding github-actions to BOT_ACCOUNTS#80759
Fix review agent duplicate replies by adding github-actions to BOT_ACCOUNTS#80759bryan-cox wants to merge 1 commit into
Conversation
…COUNTS The periodic review agent was not recognizing github-actions as a bot account, causing it to treat github-actions replies as new human activity and re-process threads every 3 hours. This produced 102+ duplicate bot replies on PR openshift#8535 alone. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: bryan-cox The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
WalkthroughTwo entries, Bot Account Recognition
🎯 1 (Trivial) | ⏱️ ~2 minutes Important Pre-merge checks failedPlease resolve all errors before merging. Addressing warnings is optional. ❌ Failed checks (1 error)
✅ Passed checks (14 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[REHEARSALNOTIFIER]
Prior to this PR being merged, you will need to either run and acknowledge or opt to skip these rehearsals. Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
@bryan-cox: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Summary
github-actionsandgithub-actions[bot]toBOT_ACCOUNTSin the periodic review agent's comment analyzerThe periodic review agent was not recognizing
github-actionsas a bot account. When the GHA workflow (which posts asgithub-actions) replied to a review thread, the periodic job's dedup logic saw it as new human activity and re-processed the thread every ~3 hours. This produced 102+ duplicate bot replies on openshift/hypershift#8535 alone, with one thread accumulating 28 identical "Done." responses over 16 days.Root Cause
The comment analyzer at line 376-412 classifies each comment as either
last_our_botorlast_actionable. A thread is flagged for re-processing iflast_actionable["createdAt"] > last_our_bot["createdAt"]. Sincegithub-actionswasn't inBOT_ACCOUNTS, its replies were classified aslast_actionable, permanently newer than anylast_our_botreply, causing infinite re-processing.Test plan
github-actionsandgithub-actions[bot]are now inBOT_ACCOUNTSgithub-actionsreplies are no longer re-processed🤖 Generated with Claude Code