Skip to content

Read merge requests and pipelines from GitLab - #2

Open
HugoHeneault wants to merge 1 commit into
HugoHeneault/gitlab-2-routingfrom
HugoHeneault/gitlab-3-reads
Open

HugoHeneault wants to merge 1 commit into
HugoHeneault/gitlab-2-routingfrom
HugoHeneault/gitlab-3-reads

Conversation

@HugoHeneault

@HugoHeneault HugoHeneault commented Oct 8, 2026 •

Copy link
Copy Markdown

🤖 Généré par Claude Opus 5.5

Step 3 of 6. Part of a stack for GitLab support, issue 4 on spatie/bloom. Each PR targets the previous step, so its diff is that step alone. Nothing changes for a project on GitHub: the characterisation tests from step 1 are never edited by later steps.

GitLab reads through glab api: routing (GitLab only on positive evidence, a GitHub remote always wins, git.forge overrides), merge request and pipeline jobs decoded into PullRequest and CheckRun, blockers from detailed_merge_status, job logs, forks' pipelines read in the source project. No database column: a merge request is found by its source branch, which survives deletion. Fixtures are real gitlab.com answers, trimmed and anonymised.

A repository whose base remote is on gitlab.com, or on a host glab is
signed in to, or whose settings say git.forge = "gitlab", now reads its
merge request, pipeline jobs and failed job logs through glab api. Any
GitHub remote, and anything uncertain, stays on GitHub.

GitLab's answers fill the existing PullRequest and CheckRun, and what
GitHub has no word for travels in blockers, which the GitHub decoder
never sets. A merge request is found by source branch, which survives
the branch being deleted, so no column is added and a GitLab number is
never written where GitHub would read it.
@HugoHeneault
HugoHeneault force-pushed the HugoHeneault/gitlab-2-routing branch from 7fd6ede to e5fc551 Compare October 13, 2026 12:35
@HugoHeneault
HugoHeneault force-pushed the HugoHeneault/gitlab-3-reads branch from eb9757b to 7527cbe Compare October 13, 2026 12:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant