GH-PR-REVIEW(1)

💅 gh-pr-review — bestie's guide to dropping a review on a PR

okay so this is the manual page for gh-pr-review from the GitHub CLI manual, and honestly? it's giving "small command, big opinions." let's get into it 🎀

---

✨ NAME ✨

gh-pr-review — add a review to a pull request. that's it. that's the whole job. slay. 💅

---

🌸 SYNOPSIS 🌸

gh pr review [<number> | <url> | <branch>] [flags]

so you point it at a PR (by number, url, or branch) and then you bless it with some flags. or don't point it anywhere and it'll figure it out. main character energy fr fr. ✨

---

🦋 DESCRIPTION 🦋

Add a review to a pull request. simple as that, bestie.

Without an argument, the pull request that belongs to the current branch is reviewed. so you literally just vibe in your branch and hit enter. the way that just works 😭💖

---

🎀 OPTIONS 🎀

• -a, --approve — approve the pull request. green check, hearts in the chat, everyone's happy 🫶
• -b, --body <string> — specify the body of a review. this is where you put your little words ✍️
• -F, --body-file <file> — read body text from file (use "-" to read from standard input). yes, the literal dash. it's iconic, it means stdin, don't overthink it 💀
• -c, --comment — comment on a pull request. no verdict, just thoughts 💭
• -r, --request-changes — request changes on a pull request. respectfully: nope, do it again 🙈

---

👑 OPTIONS INHERITED FROM PARENT COMMANDS 👑

• -R, --repo <[HOST/]OWNER/REPO> — select another repository using the [HOST/]OWNER/REPO format. inherited from the parent command, so it comes pre-loaded, like good genetics 💜

---

🔥 EXIT CODES 🔥

• 0: Successful execution — everything ate, no crumbs ✨
• 1: Error — something went sideways, bestie 💀
• 2: Command canceled — you changed your mind, valid, we respect it 🙈
• 4: Authentication required — you gotta log in first, no cap 🔑

NOTE: Specific commands may have additional exit codes. Refer to the command's help for more information.

---

🌈 EXAMPLE 🌈

# Approve the pull request of the current branch
$ gh pr review --approve

# Leave a review comment for the current branch
$ gh pr review --comment -b "interesting"

# Add a review for a specific pull request
$ gh pr review 123

# Request changes on a specific pull request
$ gh pr review 123 -r -b "needs more ASCII art"

not the "interesting" in quotes 😭 and "needs more ASCII art" — whoever wrote that was absolutely correct and should say it louder tbh. those are the exact examples, don't come for me, they're verbatim 💖

---

⭐ SEE ALSO ⭐

• gh-pr(1) — the whole gh-pr situation, go read it, it's the parent, show some respect 🧚

---

okay that's the whole page, and honestly? you ate that. go review some PRs, be kind, be specific, and remember: --approve is not a personality, but it's close. byeee 🍓

GitHub CLI v2.102.0 — Oct 2026. that's the version, that's the date, kiss kiss, mwah 💜