docs(factories): document GitLab integration - #549
Conversation
Replace nothing (new page): add factories/integrations/gitlab covering the service-account access model, group connect flow, merge_request and bot_mentioned triggers with their filters, bot mentions, run behavior on GitLab, permissions, definitions-as-code triggers, and troubleshooting. Add the page to the Factories sidebar Integrations group. Co-Authored-By: Warp <agent@warp.dev>
|
Your GitHub account is not connected to Warp. Connect it here. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
This PR was generated with Warp. Comment |
|
Your Warp account is not a member of any team with access to this repository. |
|
I'm starting a first review of this pull request. You can follow along in the session on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
There was a problem hiding this comment.
Overview
This PR adds a new Factories GitLab integration page and registers it in the Factories integrations sidebar. The page covers prerequisites, access model, setup flow, triggers, permissions, definitions-as-code syntax, and troubleshooting, and the linked standalone GitLab token setup page exists in the docs tree.
Concerns
- No blocking concerns found in the annotated diff.
- Security pass: no code or configuration changes introduce a security-sensitive runtime path, and the page documents the non-Warp-member trigger behavior and permission boundaries.
- Spec alignment:
spec_context.mdcontains no approved or repository spec context for this PR.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
Tighten compound sentences, drop em dashes from instructional text, use the gitlab-bot-mentions automation name consistently, rename the access section to 'Service accounts and access', and sharpen troubleshooting symptoms. Co-Authored-By: Warp <agent@warp.dev>
Top-to-bottom pass for brevity, directness, and clarity, mirroring the fixes from the GitHub integration doc review (PR 526): - Rewrite the intro sentence to remove the indirect 'so' framing. - Tighten the prerequisites and service-account bullets, merging redundant sentences and dropping the restated one-to-one clause. - Remove unclear colons (bot identity bullet, Actions filter cell). - Fix the setup step to name the actual web app, URL, and UI element (+ next to Factories) that opens the setup wizard, matching quickstart.mdx's and github.mdx's established terminology. - Link 'control room' to its doc page on both mentions. - Split the overloaded Automations/Triggers step into three steps. - Match github.mdx's phrasing for 'choose the projects to provide...' and the 'continues that work item instead of starting a new one' pattern. - Widen the Supported triggers table's first column (same colgroup fix as github.mdx) so 'Merge request' and 'Bot mentioned' don't wrap. - Rewrite the Permissions bullet to match github.mdx's direct three-sentence structure instead o three-sentence structure instead o three-sentence inks to absolute paths (../factory-as-code, ../connect-your-factory) matching the convention used elsewhere in factories/ docs. - Trim the 'Nothing starts work' troubleshooting entry, which dupli dupli dupli dupli dupli dupli dupli dupli dupli dupli dink back to it instead of restating it. Co-Authored-By: Warp <agent@warp.dev>
Resolves the sidebar.ts conflict from #556 (sidebar naming/grouping consistency pass), which flattened the factories Integrations group after this branch had nested a sub-group under it. Adopts the flattened structure and keeps the GitLab entry inserted right after GitHub.
Break the setup-wizard step into two: opening the wizard, then choosing the GitLab repo source and authorizing. Matches the one-action-per-step pattern applied to the rest of the procedure. Co-Authored-By: Warp <agent@warp.dev>
- Make 'Warp Factories web app' itself the hyperlink instead of spelling out the URL text separately. - Fix 'shown read-only' to 'shown as read-only'; keep Bot mentioned bolded since it names a defined trigger, consistent with how Merge request is bolded elsewhere on the page. - Add an explicit lead-in sentence before the mention-the-factory steps per suggestion. - Remove the remaining two semicolons and tighten both sentences for brevity. Co-Authored-By: Warp <agent@warp.dev>
… feedback Co-Authored-By: Warp <agent@warp.dev>
…tories-integration-gitlab
…' into hyc/factories-integration-gitlab


Documents the GitLab integration for Warp Factories, stacked into the factory-launch branch alongside the Slack (#525), Jira (#528), GitHub (#526), and Linear (#527) integration pages.
What's here
src/content/docs/factories/integrations/gitlab.mdx:<alias>-warp-<id>) with Developer access to only the factory's selected projects.merge_request(Project / Actions / Base branch filters) andbot_mentioned(Project filter;mentionedis server-seeded and read-only), plus the seededgitlab-bot-mentionsdefault automation.@oz-agenthandle or routing label; edits and Warp's own service-account activity never trigger.factory/<slug>branches, draft MRs,factory:<alias>labels, note + inline-discussion reviews, thread resolution; never merges or approves.Verification
npm run buildpasses (378 pages).style_lint --changedreports no issues for the new page.Unverified claims
GitLabWebhookStatusUnsupportedwarning and GitLab's published feature tiers, but not verified against a live GitLab plan matrix.warp-server(logic/codeforge/gitlab,model/types/triggers,logic/factorysource/defaults,client/packages/factory).