GH-CACHE-DELETE(1)

🗑️✨ GH-CACHE-DELETE (1) — the GitHub CLI manual, bestie edition ✨🗑️

okay so this is the manual page for gh-cache-delete from the GitHub CLI manual, and I'm gonna walk you through it like we're texting at 1am 💖

---

💅 NAME 💅

gh-cache-delete — Delete GitHub Actions caches. that's it, that's the whole vibe 🎀

---

🦋 SYNOPSIS 🦋

gh cache delete [<cache-id> | <cache-key> | --all] [flags]

so you give it either a cache id, or a cache key, or --all, plus whatever flags you want. pick your fighter, bestie 🫶

---

🌸 DESCRIPTION 🌸

Delete GitHub Actions caches. that's literally the whole job, and it ate 💅

but real talk — deletion requires authorization with the repo scope. no scope, no slay. periodt 🔥

---

✨ OPTIONS ✨

• -a, --all — Delete all caches. yep, ALL of them 😭 can be used with --ref to delete all the caches for one specific ref, which is lowkey the move if you don't wanna nuke everything.
• -r, --ref <string> — Delete by cache key and ref, formatted as refs/heads/ or refs/pull//merge. so you're matching on key + ref together, got it 🧚
• --succeed-on-no-caches <--all> — Return exit code 0 if no caches found. cute, right? BUT it must be used in conjunction with --all — like, it does not work solo, it needs its buddy 🙈

---

🔮 OPTIONS INHERITED FROM PARENT COMMANDS 🔮

• -R, --repo <[HOST/]OWNER/REPO> — Select another repository using the [HOST/]OWNER/REPO format. classic parent-command energy 👑

---

⭐ EXIT CODES ⭐

• 0: Successful execution — icon status 🌈
• 1: Error — it's giving oops 💀
• 2: Command canceled — you (or something) hit the brakes
• 4: Authentication required — log in, bestie 😭

NOTE: Specific commands may have additional exit codes. Refer to the command's help for more information. (yes, that's a real note, go check the help fr fr)

---

🍓 EXAMPLE 🍓

here's the part where it gets iconic — every single example, untouched, exactly as written:

# Delete a cache by id
$ gh cache delete 1234

# Delete a cache by key
$ gh cache delete cache-key

# Delete a cache by id in a specific repo
$ gh cache delete 1234 --repo cli/cli

# Delete a cache by key and branch ref
$ gh cache delete cache-key --ref refs/heads/feature-branch

# Delete a cache by key and PR ref
$ gh cache delete cache-key --ref refs/pull/<PR-number>/merge

# Delete all caches (exit code 1 on no caches)
$ gh cache delete --all

# Delete all caches for a specific ref
$ gh cache delete --all --ref refs/pull/<PR-number>/merge

# Delete all caches (exit code 0 on no caches)
$ gh cache delete --all --succeed-on-no-caches

see how --succeed-on-no-caches flips that exit code from 1 to 0? that's the whole plot twist 🎬✨

---

👑 SEE ALSO 👑

• gh-cache(1) — the parent, the main character, the source of all the inherited flags 🫶

---

k bye bestie, go clear those caches 💖 this was GitHub CLI v2.102.0, dated Oct 2026 — mwah, signed sealed delivered and prettier than the original ngl 🎀✨🦋