GH-ISSUE-VIEW(1)

πŸ’… gh-issue-view(1) β€” like, the GitHub CLI manual, bestie πŸŽ€

okay so this is gh-issue-view, straight out of the GitHub CLI manual, and it's literally the glow-up your terminal needed. sit down, grab a strawberry drink πŸ“, and let's get into it.


✨ NAME ✨

gh-issue-view β€” view an issue πŸ‘€ (yes, that's it, that's the whole vibe)


🌸 SYNOPSIS 🌸

gh issue view {<number> | <url>} [flags]

so you give it either a <number> or a <url>, pick your fighter, and then sprinkle on whatever [flags] you want. icon behavior only πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

it displays the title, body, and other information about an issue. like, the whole picture, not just a teaser. no gatekeeping here 🫢

and with the --web flag? it opens the issue in a web browser instead. browser mode activated, main character energy, periodt 🌈


πŸ‘‘ OPTIONS πŸ‘‘

  • -c, --comments β€” view issue comments. the discourse! the replies! you get to see all of it πŸ’¬
  • -q, --jq <expression> β€” filter JSON output using a jq expression. yes bestie, you can be picky about your JSON πŸ”₯
  • --json <fields> β€” output JSON with the specified fields. only the fields you asked for, nothing more, we respect boundaries ✨
  • -t, --template <string> β€” format JSON output using a Go template; see gh help formatting. fancy formatting, you love to see it πŸŽ€
  • -w, --web β€” open an issue in the browser. touch grass (the issue, in a tab) 🌱

🧚 OPTIONS INHERITED FROM PARENT COMMANDS 🧚

  • -R, --repo <[HOST/]OWNER/REPO> β€” select another repository using the [HOST/]OWNER/REPO format. it's giving "not my usual repo but make it fashion" πŸ’œ

⭐ JSON FIELDS ⭐

these are the fields you can ask for, in a big gorgeous list:

assignees, author, blockedBy, blocking, body, closed, closedAt, closedByPullRequestsReferences, comments, createdAt, id, isPinned, issueType, labels, milestone, number, parent, projectCards, projectItems, reactionGroups, state, stateReason, subIssues, subIssuesSummary, title, updatedAt, url

no cap, that's all of them. screenshot it, memorize it, put it on your wall πŸ–ΌοΈ


πŸ’€ EXIT CODES πŸ’€

  • 0: successful execution β€” slay, it worked πŸŽ‰
  • 1: error β€” it's giving chaos, something went wrong 😭
  • 2: command canceled β€” you (or something) hit the brakes πŸ™ˆ
  • 4: authentication required β€” you gotta log in first, bestie πŸ”
NOTE: specific commands may have additional exit codes. refer to the command's help for more information. iykyk πŸ“–

πŸ”₯ SEE ALSO πŸ”₯

  • gh-issue(1) β€” the parent, the icon, the blueprint πŸ‘‘

okay that's the whole page!! this one's from GitHub CLI v2.102.0, dated Oct 2026 β€” so yeah, fresh, current, and officially not me making things up πŸ’– mwah, go view some issues πŸ¦‹πŸŒΈ

πŸ“¦ where this page comes from