pr-unresolved-threads

To list unresolved GitHub PR review threads for your current branch, use a tool that queries GraphQL pullRequest.reviewThreads and filters out resolved comments. This outputs the file path, line number, author, and thread body for each open item to support review triage.

Triage unresolved inline comments on a pull request by targeting only reviewThreads that are not resolved via GraphQL pagination. This fetches human-readable summaries with file paths, line numbers, and thread bodies, excluding unrelated comment types to support fast review fixes.

Yes, you need GitHub CLI authentication to fetch unresolved PR review threads. The process uses GraphQL pullRequest.reviewThreads querying with pagination, requiring authenticated access to the repository to list open inline threads for the current branch.

The best way to find open inline review threads on a GitHub pull request is querying GraphQL reviewThreads with pagination until completion. This approach isolates unresolved threads from mixed comments and outputs file, line, author, and thread body fields for prioritization.

GraphQL pagination works when fetching unresolved PR threads by continuously querying pullRequest.reviewThreads across multiple pages until completion. This ensures all unresolved inline threads are listed, providing file, line, author, and body fields without missing open review comments.

Resolved threads are excluded when listing GitHub PR inline comments to isolate what still needs attention during review triage. By targeting only unresolved reviewThreads, the output provides file, line, author, and body fields for open items, preventing mixed comment noise.