"glab ci" fails with "The resulting pipeline would have been empty."

Checklist

  • I'm using the latest version of the extension (Run glab --version)
    • Extension version: 1.62
  • Operating system and version: openSUSE Tumbleweed 20250714
  • Gitlab.com or self-managed instance? gitlab.com
  • I have performed glab auth status to check for authentication issues
  • Run the command in debug mode (like DEBUG=true glab mr list) and attach any useful output

Summary

glab ci commands that used to work now fail with:

ERROR: could not create branch pipeline for branch master: POST https://gitlab.com/api/v4/projects/<group>%2F<group>%2F<project>/pipeline: 400 {message: {base: [The resulting pipeline would have been empty. Review the rules configuration for the relevant jobs.]}}

Example command:

glab ci run --variables part_to_run:<part> --variables environment:<env> --variables ansible_tags:<tag>

Running a pipeline with the same values from the web GUI succeeds.

glab 1.63 came out yesterday, but the changelog does not seem to indicate changes in this area. Reviewed the command and all parameters many times, cannot spot any problem. Hoping this isn't PEBKAC.

Environment

  • OS: Linux 6.15.3-2-default x86_64
  • SHELL: /bin/bash
  • TERM: xterm-256color
  • GLAB: glab 1.62.0 (1df2df0d)

Steps to reproduce

  1. Run glab ci

What is the current bug behavior?

Error "The resulting pipeline would have been empty".

What is the expected correct behavior?

Pipeline is run.

Relevant logs and/or screenshots

Additional output with DEBUG=true:

[git remote -v]
[git config --get-regexp ^remote\..*\.glab-resolved$]
[git config --get-all remote.origin.glab-resolved]
2025/07/16 18:20:11 Could not parse telemetry config value  - defaulting to 'true'
[git symbolic-ref --quiet --short HEAD]