glab(1)
π
glab runner-controller create β the glab(1) page, bestie edition β¨
Okay so listen π«Ά this is the manual page for glab runner-controller create, straight out of glab(1). Yes the name is a mouthful, no we're not shortening it, it's iconic. Sit down, grab a strawberry π, and let's get you a runner controller.
β¨ NAME β¨
glab-runner-controller-create β create a runner controller. π
(EXPERIMENTAL) β like, literally labeled experimental, we'll get to that.
π¦ SYNOPSIS π¦
glab runner-controller create [flags]
That's it. That's the whole vibe check. π
πΈ DESCRIPTION πΈ
Bestie, read this part before you go clicking anything: you must have administrator access. No admin, no controller, periodt. π
The cute part tho? The runner controller can be created in a disabled state for testing before you enable it. So you can spawn it, poke at it, and only then flip it on. Main character energy. π
But now the serious bit, and I need you to hear me: this feature is an experiment and is not ready for production use. Not me exaggerating β the page says it might be unstable or removed at any time. π So like, do NOT put your whole production setup on this and then come crying to me.
For more info on what "experimental" means here, see: https://docs.gitlab.com/policy/development_stages_support/ β go read it, iykyk. π§
π OPTIONS π
-d,--description=""β the description of the runner controller. Defaults to empty, so if you want it to have a personality you gotta give it one yourself. β¨--jq=""β filter the JSON output with ajqexpression. Defaults to empty. Perfect for when the raw JSON is giving too much and you just want the good bits. π₯-F,--output="text"β format the output as:text,json. Default istext. π--state=""β the state of the runner controller:disabled,enabled,dry_run. Defaults to empty. Go off, pick your state. π
π OPTIONS INHERITED FROM PARENT COMMANDS π
-h,--help[=false]β show help for this command. Default isfalse. Our lord and savior, the help flag. π«Ά
π EXAMPLE π
These are literal, copy them, don't retype them. π
# Create a runner controller with default settings
glab runner-controller create
# Create a runner controller with a description
glab runner-controller create --description "My controller"
# Create an enabled runner controller
glab runner-controller create --description "Production" --state enabled
Look at that first one β no flags, just vibes, defaults do everything. Slay. β
π SEE ALSO π
glab-runner-controller(1)β the parent command, go say hi to it too.
okay that's the whole page, you ate that π This little cutie was auto generated by spf13/cobra, version dated Nov 2026, and it lives in the glab(1) manual. Now go create a controller (in a disabled state, for testing, because it's experimental, bestie, we talked about this) ππ¦β¨
π¦ where this page comes from
- arch rolling: glab 1.128.0-1 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms