Problem Statement
Kaneo already integrates with GitHub and Gitea but not GitLab. I run a self-hosted GitLab CE for everything (repos, CI, registry, runners) so I can't link MRs to Kaneo tasks without writing a custom webhook bridge. Pretty sure I'm not the only one, gitlab is one of the most common self-hosted Git platforms ( at least in my circle ).
Proposed Solution
Add GitLab as a third integration option, basically the same shape as the Gitea one:
- configurable instance URL (defaults to gitlab.com, overridable for
self-hosted)
- PAT or OAuth2 auth
- pick a project by group/repo path
- import issues and MRs as task references
- sync MR status (open, merged, closed, draft) back to the task
- webhooks for live updates with HMAC signature check
It should work for both gitlab.com and self-managed.
Alternative Solutions
None that I could think worth discussing.
Relevant Context
I can test against my own self-hosted GitLab CE and GitLab.com, and send webhook payload samples if useful.
Does this feature align with Kaneo's focus on simplicity?
Yes. Same model as GitHub and Gitea (project = repo, task = issue,linked task = MR), no new UI or auth flow. If the existing integrations are behind a shared interface, GitLab is mostly an API client plus a payload mapper.
Problem Statement
Kaneo already integrates with GitHub and Gitea but not GitLab. I run a self-hosted GitLab CE for everything (repos, CI, registry, runners) so I can't link MRs to Kaneo tasks without writing a custom webhook bridge. Pretty sure I'm not the only one, gitlab is one of the most common self-hosted Git platforms ( at least in my circle ).
Proposed Solution
Add GitLab as a third integration option, basically the same shape as the Gitea one:
self-hosted)
It should work for both gitlab.com and self-managed.
Alternative Solutions
None that I could think worth discussing.
Relevant Context
I can test against my own self-hosted GitLab CE and GitLab.com, and send webhook payload samples if useful.
Does this feature align with Kaneo's focus on simplicity?
Yes. Same model as GitHub and Gitea (project = repo, task = issue,linked task = MR), no new UI or auth flow. If the existing integrations are behind a shared interface, GitLab is mostly an API client plus a payload mapper.