GitLab keeps the whole trail in one place — issues, merge requests, wikis, pipelines — which is exactly why the useful part gets buried. The reason a pipeline stage exists is in a merge request review from last spring, and the runbook for it is in a group wiki three levels up. The GitLab connector is part of askFinz Knowledge, which is still rolling out; here is what it will do, and what it will not.
Ask why a change was made the way it was
The review thread on a merge request is the closest thing most teams have to design documentation. Connected, it answers questions directly, with the merge request linked so you can read the rest.
Search group and project wikis with the issues
Wikis go stale because nobody finds them. Searching them in the same breath as issues and merge requests means the runbook surfaces when someone asks the question it answers, not only when they think to browse.
Follow an incident from issue to fix
Issue, branch, merge request, release notes. That chain is answerable as one question rather than four searches, and it stays answerable after the people involved move on.
What is read, and what is never pushed
What crosses, and what stays in GitLab
Read
issues, merge requests, comments, wikis and repository docs from the projects you select.
Written back
nonenothing. No commits, comments, labels or pipeline triggers.
Stored
a searchable copy of that text, plus a link back to the issue, MR or page.
Never read
projects you did not select, CI/CD variables, and job logs.
What you will be granting
Read-only access scoped to the groups and projects you choose, using a token that cannot write anything back.
Setting it up
Planned — not available yetWhat connecting it will look like once the connector arrives.
- 01
Authorise GitLab from Knowledge — self-managed instances are supported by URL.
- 02
Pick the groups and projects to include.
- 03
Decide the mode: discussion and wikis only, or those plus source.
- 04
Set how often to re-check.
Limits, honestly
- One-way and read-only.
- Answers reflect the last refresh, not the pipeline that just went green.
- CI variables, job logs and package registries are out of scope.
- Snippets and container registries are not included.