GitLab repository
Synchronize a GitLab project's documentation without granting write access.
Before you start
Use an account/token permitted to read the intended project and a CogLake role allowed to manage connectors. The connector uses GitLab's API to read supported files; it does not execute code or synchronize issues and merge requests.
1. Prepare a token
Use a project-scoped token where your GitLab setup supports it, or a personal token restricted to the required access. read_api covers the read API access used by this connector. A Git-only read permission must not be assumed to cover project discovery and repository listing. Do not grant write access for this import. See GitLab's token scope reference.
Confirm that the token's account can access the project and record its expiry. Self-managed instances must be reachable from CogLake with a trusted certificate; ask the operator if network access is restricted.
2. Configure CogLake
Choose Add connector → GitLab repository.
| Field | Example or meaning |
|---|---|
| Repository URL | https://gitlab.example.com/team/subgroup/handbook |
| Read-only access token | Enter the token in the secret field, not the URL |
| Branch, tag or commit | Leave empty for the default branch or select an existing ref |
| Import directory | Optional path such as docs, relative to the repository |
Use the project root, not a browser URL ending in a file view. A pinned commit will not follow new commits on a branch.
3. Test, save and synchronize
- 1Test access
- 2Select sync and scope
- 3Assign role permissions
- 4Save and import
- 5Verify one document
Start with a small documentation folder. Check a known file in the Knowledge Base and search for an exact phrase. Confirm that unrelated members cannot retrieve it.
Troubleshooting
- Unauthorized or forbidden: check token scope, project membership and token expiry.
- Project/ref not found: check the complete group path and selected branch/tag.
- Unreachable host: ask the operator to check reachability and certificate trust; do not disable TLS checks.
- Skipped content: unsupported files, generated dependencies and secret-bearing entries are not guaranteed imports. A repository connector is not a full repository backup.
For retry and incremental-sync questions, see sync and access and troubleshooting.