glab(1)

💅 glab(1) — like, the manual page for glab, bestie

okay so you opened the glab manual and landed on glab-schedule-create, which is the one that makes pipeline schedules exist. yes. brand new ones. we're creating. 🎀

---

✨ NAME ✨

glab-schedule-create — Create a new pipeline schedule.

Like, literally: this command gives birth to a brand-new CI/CD pipeline schedule and it's iconic for it. 👑

---

🦋 SYNOPSIS 🦋

glab schedule create [flags]

that's it. that's the whole thing. flags do all the heavy lifting (see below, there are six and they're all required-ish, we'll get there 🫶).

---

🌸 DESCRIPTION 🌸

okay so here's the tea: this command creates a new CI/CD pipeline schedule. and the --cron, --description, and --ref flags are required — not optional, not "if you feel like it", required, periodt. 💀

• --cron: sets the schedule's recurrence in cron syntax (yes, the star-star-star thing, you got this).
• --ref: sets the branch or tag the pipeline runs against.
• --description: provides a human-readable label, i.e. the cute little name humans read.

Wanna add pipeline variables? use --variable and pass them in key:value format. and — this is the fun part — you pass --variable multiple times to add several variables. stack 'em like bracelets. ✨

by default the schedule gets created in the current project. wanna target a different one? that's what --repo is for. no cap. 🌈

---

💅 OPTIONS 💅

• --active[=true]: whether or not the schedule is active. that's the whole vibe check.
• --cron="": cron interval pattern.
• --cronTimeZone="UTC": cron timezone. default is literally UTC because time zones are chaos and someone had to pick one. 🕰️
• --description="": description of the schedule. give it a cute label, it deserves one.
• --ref="": target branch or tag. the place your pipeline actually runs. 🏃‍♀️
• --variable=[]: pass variables to schedule in the format :. repeat flag for multiple variables. (so many colons. so many variables.) 🙈

---

🧚 OPTIONS INHERITED FROM PARENT COMMANDS 🧚

these aren't even from this command, they're heirlooms. family jewels. 💜

• -h, --help[=false]: show help for this command. when in doubt, ask the command itself.
• -R, --repo="": select another repository. you can use either OWNER/REPO or GROUP/NAMESPACE/REPO. the full URL or Git URL is also accepted. flexible queen behavior. 👑

---

🔥 EXAMPLE 🔥

# Create a scheduled pipeline that runs every hour
glab schedule create --cron "0 * * * *" --description "Hourly build" --ref main

# Create a schedule with pipeline variables
glab schedule create --cron "0 0 * * *" --description "Daily build" --ref main --variable "foo:bar" --variable "baz:qux"

look at those two. one hourly, one daily, both slaying. the second one even brought friends (foo:bar and baz:qux, we love them). ⭐

---

🍓 SEE ALSO 🍓

• glab-schedule(1) — go read the parent, it misses you.

---

ngl bestie, double-check your cron before you commit — cron syntax does not forgive and does not forget. 😭

---

✨ that's the whole page ✨ — auto generated by spf13/cobra, dated Nov 2026, and it's the glab(1) manual, so like… go forth and schedule, you absolute main character. 💖🦋