GH-REPO-DEPLOY-KEY-LIST(1)

πŸ—οΈ NAME

gh-repo-deploy-key-list β€” okay so this is the one that lists out all the deploy keys chillin' in a GitHub repository. That's it. That's the whole vibe. πŸ’…


✨ SYNOPSIS ✨

gh repo deploy-key list [flags]

πŸŽ€ OPTIONS πŸŽ€

  • -q, --jq <expression> β€” filter that JSON output through a jq expression, bestie. You know the drill. ✨
  • --json <fields> β€” spit out JSON, but only with the fields you name. No fluff, no extras, just the goods. πŸ¦‹
  • -t, --template <string> β€” format the JSON output with a Go template. and if you're sitting there like "wait, what formatting??" β€” go peek at gh help formatting, it's all there fr fr πŸ“–

πŸ’– OPTIONS INHERITED FROM PARENT COMMANDS πŸ’–

  • -R, --repo <[HOST/]OWNER/REPO> β€” this is your little shortcut to point at a different repository, using the [HOST/]OWNER/REPO format. Slay. πŸ‘‘

🌸 ALIASES 🌸

gh repo deploy-key ls

yep, ls works too β€” because typing list when you could type ls is lowkey a waste of your one precious life. 🫢


🧚 JSON FIELDS 🧚

here's the squad of fields you can ask for, exactly as they're spelled:

createdAt, id, key, readOnly, title

that's the lineup. no cap. ⭐


πŸ”₯ EXIT CODES πŸ”₯

  • 0 β€” Successful execution πŸŽ‰ (the good ending)
  • 1 β€” Error 😭
  • 2 β€” Command canceled πŸ’€
  • 4 β€” Authentication required πŸ™ˆ (go get your creds sorted, bestie)
NOTE: Specific commands may have additional exit codes. Refer to the command's help for more information. πŸ‘‘ β€” like, don't come for me if this one has extras, go read the help.

🌈 SEE ALSO 🌈


and that's the whole page, bestie! just so you're not left wondering: this is GitHub CLI v2.102.0, dated Oct 2026. periodt. πŸ’…βœ¨πŸŽ€

πŸ“¦ where this page comes from