How do I connect Lovable to GitHub?

Open your project's Settings, go to the GitHub/Git sync integration, authorise Lovable's GitHub app, and choose or create the repository to sync with — Lovable then keeps code in sync both ways automatically.

Should I connect my Lovable project to GitHub?

Yes for most real projects — it gives you a free, portable code backup and lets developers or other tools work on the code, with no real downside beyond one extra setup step.

When should I connect GitHub?

Connect it as soon as the project is more than a throwaway experiment — ideally at the start, and definitely before involving another developer, going to production, or relying on the app for a real business.

Does Lovable automatically sync with GitHub?

Yes — once connected, Git sync is automatic and two-way: changes made in Lovable push to GitHub, and commits pushed to GitHub pull back into Lovable, with no manual export step required.

Why isn't GitHub syncing with Lovable?

Usually a permissions/authorisation issue, a disconnected integration, or a conflicting edit on both sides at once — reconnect the GitHub app and check recent commits on both ends.

How do I restore an older version?

Open Version history in your Lovable project, find the version you want, and revert to it — this restores the project's code (and, if bookmarked, is easy to find again) without needing GitHub.

How do I create a backup before making changes?

Bookmark the current Version history entry before you start, and connect GitHub if you haven't already — together they give you an in-app safety net and an independent copy of the code outside Lovable.

Can developers work on Lovable code outside Lovable?

Yes — once your project is synced to GitHub, developers can clone it, edit in their own IDE, run their own build/test tools, and push changes back, all of which sync into Lovable automatically.

Can I use Cursor with Lovable?

Yes. Use Git sync to push your Lovable project to GitHub, then clone that repo and open it in Cursor for local edits, which sync back to Lovable.

Can I host Lovable code somewhere else?

Yes. You can download your project's code or sync it to GitHub via Git sync, then deploy it to any host that supports a Node/Vite React app (Vercel, Netlify, your own server, and so on).

Can I edit Lovable code directly in GitHub?

Q: Will editing GitHub break my Lovable project?

Not inherently — Git sync is designed to handle two-way edits, but structural mistakes, conflicting simultaneous edits, or breaking the build can cause problems that show up back in Lovable.

Last checked 31 Aug 2026

Short answer

Yes — once Git sync is connected, you (or a developer) can edit code directly in GitHub or your own IDE, and those changes sync back into Lovable automatically.

How it works

Git sync is genuinely two-way. Once your project is connected to a GitHub repository, you're not limited to editing through Lovable's chat or built-in Code editor — a developer can:

Clone the repository and edit in their own IDE (VS Code, JetBrains, etc.)
Push commits directly to the connected branch on GitHub
Open and merge pull requests as normal

Any of these changes get pulled back into Lovable automatically, and appear in the project as if made through Lovable itself.

After connecting GitHub, ask a developer to work on the repository in their own IDE, and confirm changes appear in Lovable once pushed.

Why you'd do this

A developer prefers their own tools, extensions, and debugging setup.
You need code changes that go beyond what's practical to prompt for (complex refactors, specific library integration).
You're running CI/CD, linting, or tests that only make sense outside Lovable's environment.

Practical considerations

Coordinate who's editing what and when — if you're prompting changes in Lovable while a developer pushes to the same files, you can hit merge conflicts.
Lovable's AI works from the current state of the code, so external changes are visible to it going forward, but it can't explain changes it didn't make.

What usually goes wrong

Two people (or a person and the AI) editing the same file simultaneously in different places, creating conflicts.
Making structural changes in GitHub that the Lovable AI later doesn't fully understand the reasoning behind, making its own follow-up edits less predictable.
Forgetting to pull the latest before starting new work locally, and overwriting recent Lovable-made changes.

See also will editing GitHub break my Lovable project for the risks specifically.

Sources

Was this answer helpful?