glab(1)

πŸ’… glab-ci-get β€” like, the glab(1) manual, but make it make sense 🫢

Okay bestie, buckle up β€” this is the glab(1) page for glab-ci-get, and it's genuinely one of the most useful little gremlins in the whole CLI. Let's get into it ✨


🌸 NAME 🌸

glab-ci-get β€” grab all the deets on a CI/CD pipeline. that's it. that's the whole job. πŸ’–


πŸ¦‹ SYNOPSIS πŸ¦‹

glab ci get [flags]

✨ DESCRIPTION ✨

So by default it goes and finds the pipeline for your current branch β€” no flags needed, she just knows. πŸŽ€ But if you'd rather point at a specific pipeline instead of fetching the latest one for a branch, use --pipeline-id.

Wanna target the head pipeline of a specific merge request by IID? That's --merge-request. And this is lowkey not the same thing as --branch β€” they diverge when the MR's head pipeline isn't the latest pipeline on its source branch. Think forks, think detached pipelines. iykyk 😭

Use --status to filter jobs by state β€” it gets passed straight through to the API's scope parameter. no cap, it's literally a passthrough.

And if you want the pipeline details as JSON? Use --output json. slay. πŸ”₯


πŸ’… OPTIONS πŸ’…

  • -b, --branch="" β€” get the pipeline for a branch. defaults to the current branch, because she's thoughtful like that 🌸
  • --jq="" β€” filter the JSON output with a jq expression. fancy brain energy 🧚
  • --merge-request=0 β€” show the pipeline for the given merge request. (the original help text literally trails off there β€” that's just how it is, bestie πŸ™ˆ)
  • -F, --output="text" β€” format the output. your options: text, json. pick your fighter πŸ‘‘
  • -p, --pipeline-id=0 β€” get the pipeline with the given. yes, it also trails off. iconic, honestly πŸ’€
  • -s, --status="" β€” show only jobs in the given state. passed through to the API's scope parameter, as previously established 🫢
  • -d, --with-job-details[=false] β€” show extended job info. more details = more better ⭐
  • --with-variables[=false] β€” show variables in the pipeline. ⚠️ heads up: this one requires the Maintainer role, so vibe check your permissions first πŸ”

🌈 OPTIONS INHERITED FROM PARENT COMMANDS 🌈

  • -h, --help[=false] β€” show help for this command. the classic "help me help you" 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. so many ways to say the same thing, we love flexibility πŸ¦‹

πŸ“ EXAMPLE πŸ“

# Get the pipeline for the current branch
glab ci get

# Get a specific pipeline by ID in another project
glab ci get -R some/project -p 12345

# Show only failed jobs for the head pipeline of MR !42
glab ci get --merge-request=42 --status=failed --with-job-details

look at her go πŸ˜­πŸ’œ


πŸ‘‘ SEE ALSO πŸ‘‘

  • glab-ci(1) β€” the parent command, go say hi 🫢

ngl the descriptions on --merge-request and --pipeline-id literally end mid-sentence in the original. that's not me, that's the manpage. i'm just the messenger πŸ’€

and that's the whole vibe check, bestie ✨ this lil masterpiece was Auto generated by spf13/cobra, dated Nov 2026, and it belongs to the glab(1) family πŸ’– go get those pipelines, you're gonna absolutely ate it πŸŒΈπŸŽ€πŸ¦‹

πŸ“¦ where this page comes from