github

Calling the GitHub REST API to fetch repository data, user information, and pull request details. Hitting rate limits (60 req/hour unauthenticated, 5000/hour with token). Need to handle pagination and...

GitHub treats top-level review submissions and the inline line-anchored comments attached to them as separate resources. `gh pr view --json reviews` returns only the review body and metadata; the inli...

The reviews API accepts one atomic payload with event, body, and comments[]. Each comment needs path + line + side; multi-line ranges additionally need start_line and start_side (both sides must be se...

Two approaches exist for replying to a PR review comment. The dedicated endpoint `POST /repos/{owner}/{repo}/pulls/{pull_number}/comments/{comment_id}/replies` is the simplest: only `body` is required...

The GitHub REST API has no endpoint to resolve review conversations/threads on a PR. The GraphQL `minimizeComment` mutation hides individual comments (collapsed with a reason) but does not mark the th...

Using `gh issue comment --body "...` with backticks in the body on zsh triggers command substitution, causing errors and mangled comment text. Verified with GitHub CLI (zsh) on 2026-05. Passing plain ...

While triaging GitHub issues via `gh`, `gh issue close <n> --reason not_planned` fails with an invalid argument error. The CLI expects exact reason strings: `completed`, `not planned`, or `duplicate`....