glab(1)

πŸ’… glab-runner-delete β€” the glab(1) glow-up πŸŽ€

okay bestie, buckle up β€” this is the glab manual page for glab runner delete, and by the end of it you're gonna be deleting GitLab runners like it's nothing. no cap. ✨


🌸 NAME

glab-runner-delete β€” literally just deletes a runner. that's the whole vibe. πŸ¦‹


✨ SYNOPSIS

glab runner delete  [flags]

that's it. that's the whole command. two spaces before [flags] and everything, we keep it exact around here πŸ’…


πŸ’– DESCRIPTION

so like β€” this permanently deletes a runner from the GitLab instance. gone. deleted. not coming back. it's giving "no undo button" energy 😭 so maybe double-check before you hit enter, mkay?

prerequisites (yes queen, there are prerequisites, read them):

  • Maintainer or Owner role β€” required for project runners. πŸ‘‘
  • Owner role β€” required for group runners. πŸ’œ
  • Administrator access β€” required for instance runners. 🫢
⚠️ the word permanently is doing a LOT of heavy lifting here. this is not a "whoopsie, undo" situation, bestie. it's giving permanent. πŸ’€

πŸŽ€ OPTIONS

  • -f, --force β€” skips the confirmation prompt. default is false, so by default it will ask you "are you sure?" first. with --force you're telling it "yeah yeah I know what I'm doing, just do it" πŸ”₯

🌈 OPTIONS INHERITED FROM PARENT COMMANDS

  • -h, --help β€” shows help for this command. default false. iconic. the classic. we love a --help. ✨

πŸ“ EXAMPLE

# Delete a runner (prompts for confirmation)
glab runner delete 6

# Skip confirmation prompt
glab runner delete 6 --force

see how it prompts you the first time and then just sends it the second time? that's the --force difference, babe. 6 is the runner id, in case that wasn't obvious πŸ’…


🧚 SEE ALSO


and that's the whole page, fr fr. no crumbs left. 🫢

⭐ cute lil sign-off: this page is auto generated by spf13/cobra, dated Nov 2026 β€” so yeah, a robot wrote the original, and I made it cute. periodt. πŸ’–πŸŽ€βœ¨
πŸ“¦ where this page comes from