[go: up one dir, main page]

`glab ci status` doesn't find branch in GDK MRs

Checklist

  • I'm using the latest version of the extension (Run glab --version)
    • Extension version: Current glab version: 1.52.0 (2025-01-20)
  • Operating system and version: Fedora 41
  • Gitlab.com or self-managed instance? gitlab.com
  • GitLab version (if self-managed) GitLab version here (Use the version endpoint, like this: gitlab.my-company.com/api/v4/version)
  • 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

For gitlab-development-kit!4362 glab ci status returns 404 for the branch.

$ DEBUG=1 glab ci status
[git remote -v]
[git config --get-regexp ^remote\..*\.glab-resolved$]
[git remote -v]
[git config --get-regexp ^remote\..*\.glab-resolved$]
[git remote -v]
[git config --get-regexp ^remote\..*\.glab-resolved$]
[git remote -v]
[git config --get-regexp ^remote\..*\.glab-resolved$]
[git symbolic-ref --quiet --short HEAD]
✘ No pipelines running or available on branch: test-fedora-bootstrap
404 Not Found

Environment

  • OS: Linux 6.12.9-200.fc41.x86_64 x86_64
  • SHELL: /bin/zsh
  • TERM: xterm-256color
  • GLAB: Current glab version: 1.52.0 (2025-01-20)

Steps to reproduce

Create MR from community fork to GDK.

What is the current bug behavior?

404

What is the expected correct behavior?

Pipeline status.

Relevant logs and/or screenshots

Possible fixes