← All integrations
Source control
GitLab, on the same adapter interface.
Source connectors implement one interface — read the tree, discover structures, resolve bindings, propose a change — so supporting GitLab is an adapter rather than a second product.
i
In short: Built on the same adapter interface as GitHub, with merge requests as the publishing path instead of pull requests.
What it is
A source-control and CI platform widely used by teams who self-host or who consolidated their DevOps tooling in one place.
What Narraxio reads
- Repository tree and file contents for authorized projects
- Branches and merge-request state
- Commit history as provenance evidence
- Webhooks for push and merge-request events
How it is connected
- an application with project-scoped access
- per-project authorization rather than group-wide
- read-only first, with write as a separate grant
- merge requests as the publishing path
How you verify it
- the same discovery report as GitHub — parsed, skipped and why
- source bindings visible per asset
- revocation in GitLab ends access immediately
Limits worth knowing
- Self-hosted GitLab needs network reachability from our workers, which is a deployment question worth raising early
- Merge-request conventions differ from GitHub's; approval rules on the GitLab side still apply and can block a publish
- Discovery only understands structures the parsers support — unsupported files are listed as skipped rather than silently ignored
Other integrations
Connect the rest of the stack
Give your content a memory. Give your AI the full picture.
Connect a repository read-only and see what has been sitting inside it — every headline, claim and near-duplicate paragraph, with the file and field each one came from.
Keep Git and your existing stack Read-only to start Narraxio runs on Narraxio