β‘ TL;DR Admins connect GitLab with the api scope and a namespace; projects then connect from Project settings, Git. Self-Managed needs your own OAuth app and IP allowlisting.
Running GitLab? Keep your Lovable projects in your own instance.
π¦ Setup
Workspace settings, Git, GitLab: add a connection, authorize with the api scope and pick a namespace. Then Project settings, Git, GitLab, Connect.
π Self-Managed
Create an OAuth app in your instance, allowlist Lovableβs IP ranges and enter the URL, Application ID and secret.
β οΈ Limits
Avoid surprises:
- β Export only
- β One branch at a time
- β Renaming or moving the GitLab project breaks sync
- β Reconnecting creates a new repo
- β Edits fail on files over 10 MB
π‘ Pro tip Never rename or move the GitLab project after connecting it.
Need self-managed Git wired into Lovable? Lord of the Wix can help. β¨
β Lovable GitLab sync FAQ
Is Self-Managed GitLab supported?
Yes.
Which scope is required?
api.
Does renaming the project break sync?
Yes.
Can I import from GitLab?
No, export only.
Does disconnecting delete the repo?
No.
π Credit: Based on public information from the Lovable documentation. Lovable is a product of Lovable. Source: docs.lovable.dev. Lord of the Wix is an independent agency and is not affiliated with Lovable.