GH-RELEASE-UPLOAD(1)

💅 gh-release-upload(1) — the GitHub CLI manual, bestie edition 🎀

okay so real talk: this is gh-release-upload, one of the gh girlies from the GitHub CLI manual, and she's here to get your files onto a release. let's go ✨

---

🌸 NAME 🌸

gh-release-upload — upload assets to a release. that's it, that's the job, and she does it gorgeously 🫶

---

🦋 SYNOPSIS 🦋

gh release upload <tag> <files>... [flags]

---

✨ DESCRIPTION ✨

so basically: you point her at a release and some files, and she uploads those asset files to a GitHub Release. main character behavior, honestly 👑

and here's a cute little trick — if you want an asset to have a display label, you just append some text starting with # after the file name. that's the whole vibe. iykyk 💅

⚠️ lowkey important: when you're using --clobber, the existing assets get deleted before the new assets are uploaded. so if the upload fails? the original assets will be lost. no cap, gone, fr fr. be careful with that one 😭

---

💖 OPTIONS 💖

• --clobber — deletes the existing assets with the same name and re-uploads them. ruthless. iconic. just remember the warning above, bestie 🙈

---

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

• -R, --repo <[HOST/]OWNER/REPO> — pick a different repository using the [HOST/]OWNER/REPO format. so you're not stuck with wherever you happen to be standing 🧚

---

⭐ EXIT CODES ⭐

vibe check on how she left things:

• 0 — successful execution, we ate 🍓
• 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.

---

🎀 SEE ALSO 🎀

• gh-release(1) — the whole release family, go say hi 💜

---

and that's the whole page, bestie — written by the GitHub CLI crew at v2.102.0, dated Oct 2026, and filed under GH-RELEASE-UPLOAD(1) in the manual. slay, go upload something pretty 💖✨