Sync your Lovable project code with GitHub or GitLab

When you build with Lovable, your project code is stored and managed inside the Lovable platform. Git sync connects a Lovable project to a repository you own on GitHub or GitLab, and keeps the two in sync automatically: changes you make in Lovable are committed to your repository, and commits pushed to the synced branch appear back in your Lovable project. This page explains how Git sync works across providers. For setup steps, see the provider pages:

• GitHub (github.com, GitHub Enterprise Cloud with data residency, or GitHub Enterprise Server)
• GitLab (GitLab.com or a self-managed GitLab instance)

​

Why sync your project to a Git repository

• Back up your code. Store your project safely outside Lovable, in an account you control.
• Collaborate with developers. Use branches, pull or merge requests, and code reviews alongside building in Lovable.
• Work locally in your IDE. Clone the repository, edit and commit locally, and push. Your changes sync back into Lovable.
• Deploy outside Lovable. Self-host or deploy to other platforms. See Deployment, hosting, and ownership options.
• Keep a copy of your code within your own infrastructure. Sync to GitHub Enterprise Cloud with data residency, GitHub Enterprise Server (both Enterprise plan), or a self-managed GitLab instance.

​

How Git sync works

Git sync has two layers, for both GitHub and GitLab:

1. A workspace connection authorizes Lovable to access a Git account, organization, group, or instance. Connections belong to the workspace and can be reused by any project in it. A workspace can hold multiple connections, including connections to both GitHub and GitLab at the same time.
2. A project repository link connects one Lovable project to one repository under one of those connections. Linking a project creates a new repository and starts two-way sync automatically.

Once linked:

• Edits made in Lovable are committed and pushed to your repository.
• Commits pushed to the synced branch flow back into your Lovable project.
• Lovable edits and syncs one branch at a time. Commits on other branches don’t appear in Lovable until you merge them into the synced branch or switch the synced branch. You can switch branches and create new branches from Lovable on both providers.

​

Who can do what

• Workspace owners and admins add, update, and delete workspace connections.
• Workspace or project owners and admins connect and disconnect projects.
• Editors and above view sync status and work with the synced repository.

The provider pages list the exact role requirements for each action.

​

Choose a provider

Each project links to one repository on one provider. Both providers support the same core two-way sync. If your team already uses one of these platforms, use that one.

​

Disconnecting and reconnecting

Disconnecting a project stops the sync, nothing more:

• Your repository stays on GitHub or GitLab, intact with all history and files.
• Your project and its code stay in Lovable. Future changes are stored only in Lovable.

If you reconnect a project later, Lovable creates a new repository with the current version of your project. The original repository stays in your account but is no longer linked.

​

Limitations

These apply to both providers:

• Export only. You can’t import an existing repository into Lovable. Connecting a project always creates a new repository.
• One repository per project. Each Lovable project links to exactly one repository.
• One branch at a time. Only the synced branch flows back into Lovable.
• Keep the repository where it is. Don’t rename, move, or delete a connected repository (or the account, organization, or group it lives in). Doing so breaks the sync.
• Reconnecting creates a new repository. You can’t re-link a previously disconnected repository.

​

FAQ