GH-ISSUE-EDIT(1)

💅 GH-ISSUE-EDIT(1) — the GitHub CLI manual, bestie edition

okay so this is the manual page for gh-issue-edit, part of the GitHub CLI manual. yes we're doing this. sit down, grab a strawberry 🍓, and let's fix your issues.

---

✨ SYNOPSIS ✨

gh issue edit {<numbers> | <urls>} [flags]

that's it. that's the whole vibe. you give it issue numbers or URLs and then you tell it what to change. 🎀

---

🌸 DESCRIPTION 🌸

Edit one or more issues inside the same repository. one repo, many issues, no chaos (mostly). 💖

🚨 real talk: editing issues' projects needs authorization with the project scope. to get that, run gh auth refresh -s project. don't skip this, it will not work and you will be sad.

🖼️ the --attach situation (lowkey iconic)

Use --attach to upload an image or video to a single issue. here's the tea:

• if you don't pass a body flag, the issue keeps the body it already has, and the attachment gets appended to it. no erasing, we're being polite.
• if the body references an attached file — like ![alt](./login.png) — that reference gets rewritten to point at the uploaded asset instead. slay.
• you can attach up to 50 files per command. fifty. that's the ceiling. 🫶

📝 alt text, explained

alt text for an image follows the path after #, like this:

--attach './login.png#The login error state'

Without it, the filename is used. and if a reference is already in the body, it keeps the alt text written there — we don't overwrite your words, bestie. 💜

Video renders as a player and has no alt text, so it cannot be given any. that's just how it is. 💀

😭 the partial-failure scenario

If some attachments upload and others fail, the issue is still updated with the ones that succeeded. the command then exits with a non-zero status, but the edited issue URLs are still printed to stdout. so like, it half-ate, but it ate. 🔥

👯 special assignee values

The --add-assignee and --remove-assignee flags both support these special values:

• @me — assign or unassign yourself
• @copilot — assign or unassign Copilot (not supported on GitHub Enterprise Server, sorry babes)

---

🎀 OPTIONS 🎀

• --add-assignee <login> — add assigned users by their login. use "@me" to assign yourself, or "@copilot" to assign Copilot.
• --add-blocked-by <number> — add 'blocked by' relationships by issue number or URL.
• --add-blocking <number> — add 'blocking' relationships by issue number or URL.
• --add-label <name> — add labels by name.
• --add-project <title> — add the issue to projects by title.
• --add-sub-issue <number> — add sub-issues by number or URL.
• --attach <file> — attach an image or video file, in '#' format.
• -b, --body <string> — set the new body.
• -F, --body-file <file> — read body text from file (use "-" to read from standard input).
• -m, --milestone <name> — edit the milestone the issue belongs to, by name.
• --parent <number> — set the parent issue by number or URL.
• --remove-assignee <login> — remove assigned users by their login. use "@me" to unassign yourself, or "@copilot" to unassign Copilot.
• --remove-blocked-by <number> — remove 'blocked by' relationships by issue number or URL.
• --remove-blocking <number> — remove 'blocking' relationships by issue number or URL.
• --remove-label <name> — remove labels by name.
• --remove-milestone — remove the milestone association from the issue.
• --remove-parent — remove the parent issue.
• --remove-project <title> — remove the issue from projects by title.
• --remove-sub-issue <number> — remove sub-issues by number or URL.
• --remove-type — remove the issue type from the issue.
• -t, --title <string> — set the new title.
• --type <name> — set the issue type by name.

---

🦋 OPTIONS INHERITED FROM PARENT COMMANDS 🦋

• -R, --repo <[HOST/]OWNER/REPO> — select another repository using the [HOST/]OWNER/REPO format. main character energy: you get to pick where you are. 👑

---

🌈 EXIT CODES 🌈

• 0 — successful execution 🎉
• 1 — error 😭
• 2 — command canceled 🙈
• 4 — authentication required 🔐

⭐ NOTE: specific commands may have additional exit codes. refer to the command's help for more information. iykyk.

---

🧚 EXAMPLE 🧚

like, actual receipts. copy these, they're exact:

$ gh issue edit 23 --title "I found a bug" --body "Nothing works"
$ gh issue edit 23 --add-label "bug,help wanted" --remove-label "core"
$ gh issue edit 23 --add-assignee "@me" --remove-assignee monalisa,hubot
$ gh issue edit 23 --add-assignee "@copilot"
$ gh issue edit 23 --add-project "Roadmap" --remove-project v1,v2
$ gh issue edit 23 --milestone "Version 1"
$ gh issue edit 23 --remove-milestone
$ gh issue edit 23 --body-file body.txt
$ gh issue edit 23 --attach './login.png#The login error state'
$ gh issue edit 23 --attach ./before.png --attach ./after.png
$ gh issue edit 23 34 --add-label "help wanted"
$ gh issue edit 23 --type Bug
$ gh issue edit 23 --remove-type
$ gh issue edit 23 --parent 100
$ gh issue edit 23 --remove-parent
$ gh issue edit 100 --add-sub-issue 123,124
$ gh issue edit 123 --add-blocked-by 200 --add-blocking 300,301

notice that last one edits 123 and adds relationships to 200, 300, and 301? multi-issue behaviour at its finest. 💅

---

👀 SEE ALSO 👀

• gh-issue(1) — go read the main one, bestie, it's the parent.

---

and that's the whole page!! 🫶 this was GitHub CLI v2.102.0, dated Oct 2026 — consider yourself signed off, mwah 💖✨🎀