Skip to content

GitLab onboarding, settings, sign in and rebase - #4

Open
HugoHeneault wants to merge 5 commits into
HugoHeneault/gitlab-4-actionsfrom
HugoHeneault/gitlab-5-onboarding
Open

HugoHeneault wants to merge 5 commits into
HugoHeneault/gitlab-4-actionsfrom
HugoHeneault/gitlab-5-onboarding

Conversation

@HugoHeneault

@HugoHeneault HugoHeneault commented Oct 8, 2026 •

Copy link
Copy Markdown

🤖 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_username branch prefix, GitLab accounts in Agents and GitLab prompts in prompt settings. The settings rows appear only when glab is installed.

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
HugoHeneault force-pushed the HugoHeneault/gitlab-5-onboarding branch from 0dcd5c7 to d799282 Compare October 8, 2026 10:26
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