Sync your Lovable project code with GitHub, GitLab, or Bitbucket

1. 1

   Go to your project's settings, then find the 'Git' tab.

   This is where you manage the connection between your Lovable project and your code repository.

2. 2

   Choose your preferred code hosting service (GitHub, GitLab, or Bitbucket) and follow the specific setup instructions for that service.

   Each service has slightly different steps to authorize Lovable to access your account and create a new repository for your project.

3. 3

   After connecting, make changes in Lovable as usual, or clone the new repository to your computer and make changes there.

   Lovable automatically keeps your project and the connected repository in sync, so changes made in either place will reflect in the other.

I need to connect my Lovable project to a new GitHub repository for backup and collaboration. Please set up two-way Git sync for this project with GitHub.

Git sync

A feature that automatically keeps your Lovable project's code identical to the code in a separate online storage location (like GitHub), updating both sides whenever changes are made.

repository

An online folder where your project's code and its entire history of changes are stored.

IDE

A special program on your computer that helps you write, test, and fix computer code more easily.

commit

A snapshot of your code at a specific point in time, along with a message describing the changes made.

branch

A separate version of your project's code that you can work on without affecting the main version, useful for trying out new features or fixes.

pull request / merge request

A way to propose changes from one branch to another, often used for team review before combining code.

force-push, rebase, squash commits

Advanced Git actions that rewrite the history of changes in your code. These can cause problems with Lovable's sync if used on the main synced branch.

commit attribution

The process of recording who made a specific change (commit) to the code, often showing their name or email address.

• Do not force-push, rebase, or squash commits on the synced branch, as this can cause Lovable to lose its own changes.
• Be aware that email addresses in commit messages are publicly visible if your repository is public, so consider disabling commit attribution for public projects.
• Remember that Git sync exports your code but does not deploy your live site; you still need to publish from Lovable.
• Understand that your database content is not included in the repository, only the files that define its structure.
• Do not expect to import an existing repository into Lovable; Git sync always creates a new repository.
• If you rename or move a GitLab project or group, the sync will break.
• If you disconnect a project and then reconnect it, Lovable will create a *new* repository, not re-link to the old one.