GH-ISSUE-TRANSFER(1)

💅 GH-ISSUE-TRANSFER(1) 💅

okay bestie, welcome to the GitHub CLI manual — this is the page for gh-issue-transfer, and honestly? it's giving "small command, big main character energy" ✨

---

🌸 NAME 🌸

gh-issue-transfer — move an issue over to a whole other repository 🦋

like, packing up your little issue and sending it to live somewhere new, no cap.

---

🎀 SYNOPSIS 🎀

gh issue transfer {<number> | <url>} <destination-repo> [flags]

so you gotta hand it either an issue <number> or an issue <url>, plus the <destination-repo> where it's headed, plus whatever [flags] you're feeling 💖

---

✨ OPTIONS INHERITED FROM PARENT COMMANDS ✨

these aren't even this command's own options, they're handed down from the parent, and they ate fr fr:

• -R, --repo <[HOST/]OWNER/REPO> — pick a different repo using that [HOST/]OWNER/REPO format 🫶 like, "not this repo, that one."

---

🔥 EXIT CODES 🔥

vibe check on how it went — memorize these, iykyk:

• 0: Successful execution 👑 it slayed, it worked, we love to see it
• 1: Error 😭 something went wrong
• 2: Command canceled 🙈 you (or something) hit the brakes
• 4: Authentication required 💀 you gotta log in first bestie, no way around it

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

like, these are the general ones — some commands got extra exit codes of their own, so check that command's help for the full tea 🍓

---

🌈 SEE ALSO 🌈

• gh-issue(1) — the big sibling page, go read it 💜

---

and that's the whole thing, bestie ✨🦋 no notes, iconic behavior. this page came from GitHub CLI v2.102.0, dated Oct 2026 — so if your version's different, that's a whole other era 💅🎀