Repository navigation
Create, merge and fix merge requests through the agent on GitLab - #3
Open
HugoHeneault wants to merge 2 commits into
Open
HugoHeneault wants to merge 2 commits into
HugoHeneault wants to merge 2 commits into
Conversation
GitLab projects get their own defaults: the merge request instructions (glab mr create), the merge steps (glab mr merge --auto-merge=false --sha), and GitHub's other prompts in GitLab's words. Overrides live under prompts.gitLab.<id>, so a GitHub template never reaches a GitLab project. GitHub's defaults, keys and turns are unchanged. A workspace can start from !12 or a merge request URL, and the inspector names the forge it is talking to.
Bloom's direct routes ran gh only, and merging directly is the default, so a GitLab merge request would have gone to gh pr merge. GitLab now gets the same routes through glab: create from the pushed commits, and merge the confirmed head with --sha and --auto-merge=false. glab's --rebase rebases and then refuses its own --sha, so a rebase runs first and its new head is merged only if it replayed the confirmed commits. The checks before a direct merge are shared, in GitHub's words for GitHub.
HugoHeneault
force-pushed
the
HugoHeneault/gitlab-4-actions
branch
from
October 13, 2026 12:35
bf076c6 to
1f92471
Compare
HugoHeneault
force-pushed
the
HugoHeneault/gitlab-3-reads
branch
from
October 13, 2026 12:35
eb9757b to
7527cbe
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 Généré par Claude Opus 5.5
Step 4 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.
Create, merge and fix conflicts through the agent on GitLab: GitLab defaults for the instructions (
glab mr create ... --yes,glab mr merge --auto-merge=false --sha) and GitHub's prompts in GitLab's words, overrides underprompts.gitLab.<id>,!12and merge request URLs on GitLab projects only, and the inspector naming the forge. GitHub's defaults and turns are unchanged and pinned.