Repository navigation
GitLab onboarding, settings, sign in and rebase - #4
Open
HugoHeneault wants to merge 5 commits into
Open
HugoHeneault wants to merge 5 commits into
HugoHeneault wants to merge 5 commits into
Conversation
When a GitLab read fails because glab is missing or signed out, the inspector names GitLab and offers the sign in sheet, which runs brew install glab or glab auth login --hostname <host>. The sheet's GitHub words are unchanged. A merge request GitLab will only merge once rebased offers Rebase, which asks the agent to run glab mr rebase and nothing more.
HugoHeneault
force-pushed
the
HugoHeneault/gitlab-5-onboarding
branch
from
October 8, 2026 10:26
0dcd5c7 to
d799282
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
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 5 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.
Onboarding and settings: an optional "GitLab CLI" onboarding row (the one deliberate change visible to GitHub users, never in the verdict), GitLab sign in from the inspector, Rebase when GitLab requires it, "Hosted on" in project settings,
gitlab_usernamebranch prefix, GitLab accounts in Agents and GitLab prompts in prompt settings. The settings rows appear only whenglabis installed.