Integration
Connect GitLab to your delivery record
Merge requests and pipeline results stop living in a separate tab. A merge request that references a Stride issue surfaces on that issue, with its pipeline state, so the backlog reflects what CI actually says rather than what someone remembered to update.
What connecting gives you
- Merge requests linked to issues — reference the issue and the link is made for you.
- Pipeline status on the story — the CI verdict lands where the work is tracked.
- A project allowlist — Stride only watches the GitLab projects you name.
- Signature-verified webhooks — every payload is checked before it is processed.
What it does not do — worth reading before you plan around it
The GitLab integration is deliberately narrower than the GitHub one. Today it consumes exactly two event types, and it never writes.
| Capability | GitLab | GitHub |
|---|---|---|
| Merge / pull request events | Yes | Yes |
| Pipeline / CI status | Yes | Via checks on the PR |
| Push events | No | Yes |
| Open a draft PR / MR from a story | No | Yes, including over MCP |
If draft-MR creation from a story matters to your workflow, say so — it is a known gap rather than a deliberate omission. The GitHub integration is the deeper of the two today.
Frequently asked questions
How do I connect GitLab to Stride?
Open Settings → Integrations → GitLab, supply the connection details, and pick the projects Stride may watch. Stride registers a webhook against those projects and verifies the signature on every payload it receives.
Which GitLab events does Stride consume?
Two: merge request events and pipeline events. That is the whole surface today — Stride does not consume issues, commits, releases, or deployments from GitLab.
Does this match the GitHub integration feature for feature?
No, and it is worth knowing before you plan around it. GitHub additionally consumes push and installation events and supports opening a draft pull request from a story. GitLab covers merge requests and pipelines only, and has no outbound write.
Can Stride write back to GitLab?
No. This is an inbound integration. Stride reads what GitLab reports and never modifies your merge requests, branches, or pipelines.
Can I limit which projects Stride sees?
Yes — an explicit project allowlist, managed from the same settings screen. Projects outside it are never watched, and changing the list does not require reconnecting.