Connect GitLab
Connect a GitLab project or group to Korvu so merge requests are reviewed automatically.
Korvu treats GitLab merge requests the same way it treats GitHub pull requests — webhook in, review out. The connect flow is slightly different because GitLab doesn't have GitHub-style apps.
Requirements
- A GitLab account with Maintainer or Owner on the project or group you want to connect
- A Korvu workspace — Cloud is on a waitlist pre-GA; self-hosted Core works today
Connect via the Korvu app
- From the Korvu app, click Connect GitLab.
- Sign in to GitLab and authorize Korvu's OAuth app.
- Pick the project or group to connect.
- Korvu installs a project hook for merge-request events and (optionally) a deploy-key for read access.
What Korvu installs
When you connect a project, Korvu adds two things to GitLab:
- A project hook that fires on merge request events (open, update, reopen)
- A deploy key with read access, so Korvu can fetch diff content
When you connect a group, Korvu repeats the same setup for every project in the group, and watches for new projects to enroll them automatically.
Self-hosted GitLab
Korvu supports self-hosted GitLab via a custom GitLab URL. From the connect screen, click Self-hosted GitLab and enter your instance URL. The OAuth + project-hook flow is otherwise identical.
Network reachability Your self-hosted GitLab must be reachable from Korvu's public endpoints. If your instance is behind a VPN, run Korvu Core as a hybrid worker inside your network instead.
Disconnecting
Disconnecting a project removes the project hook and deploy key. Korvu retains historical review metadata for 30 days; diff content was never retained.