Skip to content

Ask for pull requests through a forge client - #1

Open
HugoHeneault wants to merge 1 commit into
HugoHeneault/add-gitlab-supportfrom
HugoHeneault/gitlab-2-routing
Open

HugoHeneault wants to merge 1 commit into
HugoHeneault/add-gitlab-supportfrom
HugoHeneault/gitlab-2-routing

Conversation

@HugoHeneault

@HugoHeneault HugoHeneault commented Oct 8, 2026 •

Copy link
Copy Markdown

🤖 Généré par Claude Opus 5.5

Step 2 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.

A ForgeClient protocol for the operations a project could need from another forge, with GitHubForge forwarding to GitHub unchanged, and ForgeResolver answering GitHub for every repository. Call sites go through the resolver. GitHub.swift is not touched and no default moves.

ForgeClient names the operations a project could need from a forge other
than GitHub: reading its pull request and checks, a failed run's log,
marking ready, listing, summarising and checking one out. GitHubForge
forwards each to GitHub unchanged, and ForgeResolver answers it for
every repository, so no command, default or answer moves. Creating a
repository stays on GitHub alone.
@HugoHeneault
HugoHeneault force-pushed the HugoHeneault/add-gitlab-support branch from b69b32f to 75ffe2a Compare October 13, 2026 12:35
@HugoHeneault
HugoHeneault force-pushed the HugoHeneault/gitlab-2-routing branch from 7fd6ede to e5fc551 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