[go: up one dir, main page]

fix(ci status): detect branch repo from remote

Description

  • fix(ci status): detect branch repo from remote

Related Issues

Resolves #7735 (closed)

How has this been tested?

When creating this MR.

$ DEBUG=1 ./bin/glab ci status
[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]
2025/01/23 05:12:30 [Current branch: fix-fork-status]
[git config --get-regexp ^branch\.fix-fork-status\.(remote|merge)$]
[git remote -v]
[git config --get-regexp ^remote\..*\.glab-resolved$]
2025/01/23 05:12:30 [Repository: gitlab-community/cli]
✘ No pipelines running or available on branch: fix-fork-status
No pipeline running or available for ref fix-fork-status

After creating the MR.

$ DEBUG=1 ./bin/glab ci status
[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]
2025/01/23 05:13:25 [Current branch: fix-fork-status]
[git config --get-regexp ^branch\.fix-fork-status\.(remote|merge)$]
[git remote -v]
[git config --get-regexp ^remote\..*\.glab-resolved$]
2025/01/23 05:13:25 [Repository: gitlab-community/cli]
(created) • not started test            run_tests
(created) • not started test            lint
(created) • not started test            lint_commit
(running) • 00m 06s     test            danger-review
(created) • not started test            secret_detection
(created) • not started test            gemnasium-dependency_scanning
(created) • not started test            gitlab-advanced-sast
(running) • 00m 06s     documentation           check_docs_markdown
(running) • 00m 06s     documentation           check_docs_update

https://gitlab.com/gitlab-community/cli/-/pipelines/1637116929
SHA: c2764f5a377129c20f030a6c76adf8906b3a8874
Pipeline state: running

Screenshots (if appropriate):

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation
  • Chore (Related to CI or Packaging to platforms)
  • Test gap
Edited by Anatoli Babenia

Merge request reports

Loading