Using GitHub API with gh CLI

Use gh api with the REST endpoint /repos/{owner}/{repo}/pulls/{pull_number}/comments to fetch inline review comments. The gh CLI tool retrieves comment metadata including ID, file path, line number, body, author, and timestamps without requiring manual API authentication or token management.

Yes. Use gh api with GraphQL queries to fetch review thread structure and resolved/unresolved status. This retrieves thread state data not exposed by standard gh pr view commands, enabling automated filtering of active vs. resolved review conversations.

REST endpoints like /repos/{owner}/{repo}/pulls/{pull_number}/reviews return flat comment lists; GraphQL queries expose nested thread structure and resolution status. Choose REST for simple comment extraction and GraphQL when you need hierarchical review data or advanced filtering across thread relationships.

No, jq is optional. The gh CLI returns JSON by default; jq enhances filtering and formatting of results. Use the -q flag with gh api to pipe output through jq for selective field extraction, or parse JSON responses directly in your automation script.

Parse the URL pattern https://github.com/{owner}/{repo}/pull/{pr_number} to extract these identifiers, then pass them to gh api endpoints. Most automation workflows extract these values from environment variables or git remote URLs to make API calls dynamic and reusable.

gh pr view displays basic PR metadata but omits inline review comments and thread status. Use gh api directly to access full REST and GraphQL endpoints, retrieving granular comment data, resolver information, and thread resolution states for comprehensive review analysis.