glab(1)

📦
version 1.128.0 · 12 versions
, in arch rolling

hey bestie 💕 welcome to glab(1) — this page is all about glab-ci-trigger, the lil command that gets a manual CI/CD job moving. No cap, it's giving very "press the button, bestie" energy. 🎀

💖 NAME

glab-ci-trigger — trigger a manual CI/CD job. That's literally the whole vibe: it triggers a manual CI/CD job. ✨

🌸 SYNOPSIS

glab ci trigger [] [flags]

🦋 DESCRIPTION

okay so here's the tea ☕: if you don't give it a job argument, you can pick one interactively. Super easy, very choose-your-own-adventure.

Important caveat, bestie: you can trigger only jobs with manual status. That's the vibe check this command enforces. 💅

🎀 OPTIONS

  • -b, --branch="" — the branch to search for the job on. If you leave it blank, it defaults to the current branch. 🌿
  • -p, --pipeline-id=0 — the pipeline ID to search for the job. 🔎

🌈 OPTIONS INHERITED FROM PARENT COMMANDS

  • -h, --help[=false] — show help for this command. Your classic "wait, what does this do again?" button. 🫶
  • -R, --repo="" — select another repository. You can use either OWNER/REPO or GROUP/NAMESPACE/REPO, and the full URL or Git URL is also accepted. Iconic flexibility, honestly. 👑

🔥 EXAMPLE

# Interactively select a job to trigger
glab ci trigger

# Trigger a manual job by ID
glab ci trigger 224356863

# Trigger a manual job by name
glab ci trigger lint

⭐ SEE ALSO

  • glab-ci(1) — go check out the parent command too, bestie 💜

mwah 💋 this page was auto generated by spf13/cobra, dated Nov 2026, and it's living its best life as part of glab(1). bye bestie, go trigger something manual 🫶✨

📦 where this page comes from