glab(1)

🌸 glab(1) — or: how to run a CI/CD pipeline trigger and look iconic doing it 🌸

okay bestie, welcome to the glab manual 💅 this particular page is the one for glab-ci-run-trig, and no I did not make that name up, it's giving keyboard smash but it's real. grab a strawberry drink 🍓 and let's get into it.

---

✨ NAME ✨

glab-ci-run-trig — Run a CI/CD pipeline trigger. that's it. that's the whole job. she triggers pipelines. periodt.

---

🦋 SYNOPSIS 🦋

glab ci run-trig [flags]

---

💖 DESCRIPTION 💖

Use --token to give it a pipeline trigger token. If you're like "no bestie I'm not passing a token", then the CI_JOB_TOKEN environment variable absolutely has to be set. no token, no pipeline, no vibes. 😭

Use --branch to pick a branch or reference. If you don't say anything, it defaults to the current branch. main character energy: default edition.

Now the fun part ✨ — you can pass one or more pipeline inputs using the -i or --input flag, one flag per input. Every single input flag uses the format key:value. that's the whole shape, iykyk.

The values are typed, and they'll default to string unless you explicitly say otherwise. To specify a type, use the type(value) syntax. For example, key:string(value) will pass the string value as the input. slay.

Valid types are, and this is literally the whole list, don't come for me:

• string — A string value. This is the default type. For example, key:string(value). the no-effort option, we respect her.
• int — An integer value. For example, key:int(42).
• float — A floating-point value. For example, key:float(3.14).
• bool — A boolean value. For example, key:bool(true).
• array — An array of strings. For example, key:array(foo,bar).

An array of strings can be specified with a trailing comma 🎀. For example, key:array(foo,bar,) will pass the array [foo, bar]. array() specifies an empty array. To pass an array with the empty string, use array(,). yes the empty string gets her own little slot, she's valid too.

⚠️ Value arguments containing parentheses should be escaped from the shell with quotes. For example, --input key:array(foo,bar) should be written as --input 'key:array(foo,bar)'. do NOT let your shell eat your parens bestie, it will and then you'll be sad 😭

---

👑 OPTIONS 👑

• -b, --branch="" — Create pipeline on branch or reference. (the original even has that little space before the period, we love her, keeping it 💅)
• -i, --input=[] — Pass inputs to pipeline in format ':'. Cannot be used for merge request pipelines. See documentation for examples. like actually cannot, don't try it.
• -t, --token="" — Pipeline trigger token. Can be omitted only if the CI_JOB_TOKEN environment variable is set.
• --variables=[] — Pass variables to pipeline in the format :. Multiple variables can be comma-separated or specified by repeating the flag. choose your own adventure, both are valid 🫶

---

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

these aren't hers, she inherited them, but we still love them:

• -h, --help[=false] — Show help for this command.
• -R, --repo="" — Select another repository. You can use either OWNER/REPO or GROUP/NAMESPACE/REPO. The full URL or Git URL is also accepted. so many options, so much flexibility, we're obsessed.

---

🔥 EXAMPLE 🔥

glab ci run-trig -t xxxx
glab ci run-trig -t xxxx -b main

# Specify CI variables
glab ci run-trig -t xxxx -b main --variables key1:val1
glab ci run-trig -t xxxx -b main --variables key1:val1,key2:val2
glab ci run-trig -t xxxx -b main --variables key1:val1 --variables key2:val2

# Specify CI inputs
glab ci run-trig -t xxxx -b main --input key1:val1 --input key2:val2
glab ci run-trig -t xxxx -b main --input "replicas:int(3)" --input "debug:bool(false)" --input "regions:array(us-east,eu-west)"

look at that last one. replicas:int(3), debug:bool(false), regions:array(us-east,eu-west) — typed, quoted, unbothered. ate and left no crumbs 💅✨

---

🧚 SEE ALSO 🧚

• glab-ci(1) — the mothership. go read her next, bestie.

---

💀 head's up: glab ci run-trig does not work with merge request pipelines when you're using -i/--input. that's a hard no, not a vibe check you can fail and retry.

---

okay that's the page!! you now know literally everything this command knows, no gatekeeping, no cap 💜

this little manual page was Auto generated by spf13/cobra, dated Nov 2026, and it's the glab(1) page — mwah, go trigger something iconic 🎀✨