Conversation
…ents Review-and-fix loops previously needed separate pr_get, run_list, and raw comment/review API calls per PR. pr_status fetches PR detail, CI check runs, review verdicts (incl. bot reviewers like CodeRabbit), line comments, and issue-level comments in one MCP round trip, and returns a single JSON payload. Known limitation: the REST API has no isResolved field for review threads (GraphQL-only), so review_comments includes resolved threads too -- callers should use judgment on older/superseded ones.
Two problems with the first pass: REST has no thread-resolution field at all (only GraphQL's reviewThread.isResolved), so old-but-fixed review comments were indistinguishable from live ones; and every call re-fetched full comment history with no way to ask for just what's new. - pulls::resolved_review_comment_ids: GraphQL lookup of resolved review-thread comment ids; pr_status filters review_comments against it so only unresolved (still-outstanding) ones survive. - since (ISO8601) on GitHubRequest, threaded into the REST comment fetches (both support ?since= server-side) so repeated pr_status calls only pull what's new since the caller's last check. - Output trimmed to what a fix loop actually needs: passing checks become a count instead of a list, reviews dedupe to one entry (the latest) per reviewer, and timestamps/html_url/redundant fields are dropped entirely.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (8)
📝 WalkthroughWalkthroughChangesPull request status
Estimated code review effort: 4 (Complex) | ~45 minutes Sequence Diagram(s)sequenceDiagram
participant Request as MCP request
participant Handler as flare_git_impl
participant GitHub as GitHub APIs
participant Formatter as pr_status_json
Request->>Handler: dispatch pr_status
Handler->>GitHub: fetch PR status data
GitHub-->>Handler: return checks, reviews, and comments
Handler->>Formatter: assemble collected data
Formatter-->>Handler: return trimmed JSON
Handler-->>Request: return PR status
Possibly related PRs
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
⚔️ Resolve merge conflicts
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 |
|
Redundant auto-open from on BY-oyXH4yNNaLC2iYP2Uh (item #218). That work was already recovered and merged via PR #269, with item #220 tracking its review — both already closed. This PR's branch () contains unrelated leftover content (GitHub API integration files), not the flare_handoff feature the item describes. Closing without merge; not touching the branch itself pending manual review. |
|
Correction (previous comment lost text to shell backtick expansion): this PR was auto-opened by the "item done" action on item #218. That work was already recovered and merged via PR #269, with item #220 tracking its review — both already closed. This PR's branch (task/218) contains unrelated leftover content (GitHub API integration files), not the flare_handoff feature item #218 describes. Correctly closed without merge. |
Auto-opened on
item donefor BY-oyXH4yNNaLC2iYP2Uh.Summary by CodeRabbit
New Features
pr_statusaction that summarizes pull request checks, reviews, unresolved review comments, and issue comments.sincefiltering for comment history.Documentation
pr_statusand its filtering options.