refactor: remove requestBotReview — GitHub silently drops bot reviewer requests#23
Conversation
…r requests Live-probed on a throwaway PR: the requestReviews GraphQL mutation returns success but never lands a request for third-party app bots (no pending request, no timeline event) — with the app token or an admin user token alike. Requested-reviewer state is reserved for users, teams, and GitHub-native bots (Copilot), so this was two network calls per run plus a misleading success log. PrContext.nodeId and the OctokitLike users.getByUsername surface go with it — requestBotReview was their only consumer. The [bot][bot] double-suffix regression coverage moves to the fetchBotIssueComments suite; viewer-memoization coverage now spans fetchBotIssueComments + upsertSummaryComment. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
umm-actually reviewed at No findings above threshold. umm-actually · deepseek/deepseek-v4-pro |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (7)
💤 Files with no reviewable changes (6)
📝 WalkthroughWalkthroughThe PR removes bot review requests and PR node identity from GitHub client and event context contracts. It updates orchestration and client test doubles, adjusts affected expectations, and adds coverage for bot-login suffix handling and viewer-query memoization. ChangesGitHub review flow
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What
Removes
requestBotReview(Step 3.5), its GraphQLrequestReviews/botIdsplumbing,botNodeIdSchema, theusers.getByUsernamesurface onOctokitLike, andPrContext.nodeId(its only consumer).Why
Live-probed on a throwaway PR (#22): the mutation returns success but never lands a request for third-party app bots — no pending review request, no timeline event — whether called with the app installation token or an admin user token. GitHub reserves requested-reviewer state for users, teams, and its own Copilot bot; ineligible reviewers are silently dropped. CodeRabbit/Sourcery never hold this state either — their sidebar presence comes from posted reviews, which umm-actually already has.
So this was two network calls per run plus a
requested bot reviewsuccess log that misled every investigation of the feature.Coverage moves
[bot][bot]double-suffix regression guard →fetchBotIssueCommentssuite (the bug's actual blast radius)fetchBotIssueComments+upsertSummaryComment311 tests, lint/build/prettier clean.
🤖 Generated with Claude Code
Summary by CodeRabbit
[bot]suffixes.