GitLab Planned
A native GitLab connector is on the roadmap. It will sync commit history, merge requests and issues into evidence — read-only, mapped to the claim, the same model as the GitHub App. Until it ships, you can reference GitLab items by link or upload an export, and they become evidence tied to the project.
What SREDlog takes in
- Planned: commit messages, timestamps, authorship and merge-request activity
- Today: the GitLab links you reference, or the contents of an export you upload
What it never touches
- Your source code will not be stored — the connector reads activity, not your codebase
- No write access: SREDlog will never push to or change anything in GitLab
- Nothing is retrieved today that you don't link or upload yourself
Evidence type
Commit history, merge requests, issues
How it connects
Planned: native read-only sync. Today: reference by link or upload an export.
Authentication
Planned: least-privilege OAuth, read-only. Today: none — you provide the link or file.
Security
The planned connector will use least-privilege, read-only OAuth the client grants and can revoke. No credentials are stored today.
Available on
All plans
Last verified
2026-07-15
Setting it up
- 1Today: copy the links to the relevant GitLab commits, merge requests or issues, or export them.
- 2Add them to the project's evidence as a link or upload, and tie each to the SR&ED project.
- 3When the native connector ships, you'll authorize read-only access and map projects to claims — no link-pasting.
Related: Evidence management · All integrations
Bring your GitLab evidence into a claim
Start a free trial and turn the work you already track into an audit-ready SR&ED claim.
3-day free trial · No credit card required