GH-SECRET(1)

💖 GH-SECRET(1) — the gh secret glow-up 💖

okay bestie, so this is the <pink>gh-secret</pink> page from the GitHub CLI manual (that's gh-secret(1) if you're being all formal about it) — and honestly? it's giving ✨ secrets management ✨ and we're gonna get you fluent in it.

---

🌸 NAME 🌸

gh-secret — literally the way you manage GitHub secrets. that's it, that's the vibe. 🔐

---

🦋 SYNOPSIS 🦋

gh secret <command> [flags]

---

✨ DESCRIPTION ✨

so here's the tea, bestie: secrets can be set at the repository level or the organization level, and they get used in GitHub Actions, Agents, or Dependabot. 👑

and there's more — user, organization, and repository secrets can be set for use in GitHub Codespaces. meanwhile environment secrets can be set for use in GitHub Actions. different secret, different little home, iykyk 🏠

want to actually get started instead of just vibing? run gh help secret set and it'll walk you through it. go off. 💅

---

🎀 AVAILABLE COMMANDS 🎀

• gh-secret-delete(1) — delete secrets. bye-bye, begone, no cap 🗑️
• gh-secret-list(1) — list secrets. let's see what we're working with 👀
• gh-secret-set(1) — create or update secrets. the main character command fr fr ⭐

---

💜 OPTIONS 💜

• -R, --repo <[HOST/]OWNER/REPO> — select another repository using the [HOST/]OWNER/REPO format. yes, that's the whole format, brackets and all — respect it 🫶

---

🔥 EXIT CODES 🔥

these are not a vibe check you wanna fail, so memorize them:

• 0 — successful execution. slay, you ate 🎉
• 1 — error. something went sideways 😭
• 2 — command canceled. you (or something) hit the brakes 💀
• 4 — authentication required. go log in, bestie 🙈

NOTE: specific commands may have additional exit codes. refer to the command's own help for more info — lowkey always worth a peek 👑

---

🌈 SEE ALSO 🌈

• gh(1) — the parent page, the main character, the icon 👑

---

and that's the whole page, bestie — you're officially a secret-keeper now 🧚

made with love from the GitHub CLI v2.102.0 era, dated Oct 2026 — mwah 💋