Short answer
Check the sync status before you push anything. If Lovable says the branch has diverged, your next push replaces Lovable’s version, and edits made only in Lovable drop out of the project. Lovable saves a backup first, but don’t rely on it: keep a copy of those edits before you push. Otherwise, find your symptom below; often it comes down to which branch is synced.
Find your symptom
01
The status says diverged: read this before you push
“the push replaces Lovable's version of the branch with the GitHub version” Lovable, GitHub integration
When Lovable and GitHub have diverged, the next push replaces Lovable’s version of the branch, and the project no longer contains edits made only in Lovable. Lovable saves a backup first and the project owner can restore it, but check what is on the lovable-sync branch and copy any Lovable-only changes across before you push.
02
Commits on another branch don’t show up
“Lovable only syncs one branch at a time, and that is the branch the project is currently set to” Lovable, GitHub integration
Lovable syncs only the branch the project is set to. Merge your work into that branch, or switch the synced branch in Lovable.
03
GitHub has commits Lovable never pulled
“Lovable pulls your changes when GitHub notifies it about a push to the synced branch.” Lovable, GitHub integration
Lovable pulls when GitHub tells it about a push to the synced branch, and reconnecting doesn’t trigger a pull. If the status doesn’t say diverged, push a new commit, even an empty one: git commit --allow-empty -m "Trigger Lovable sync", then git push.
04
Lovable’s work landed on a lovable-sync branch
“To avoid losing your work, Lovable pushed it to a branch named lovable-sync instead.” Lovable, GitHub integration
GitHub rejected Lovable’s push, so Lovable saved the work to a branch called lovable-sync instead. Review that branch and merge it through a pull request.
05
A new fallback branch appeared
“Someone deleted the synced branch on GitHub.” Lovable, GitHub integration
The synced branch was deleted on GitHub, so Lovable moved the project to a new fallback branch to keep you editing. Switch the synced branch back once the branch you want exists again.
06
Sync stopped after adding a large file
“Lovable itself cannot save files larger than 10 MB into your project.” Lovable, GitHub integration
GitHub rejects pushes with files over 100 MB, and Lovable can’t save files over 10 MB into a project. Delete the listed files from the project, or ask Lovable to remove them, and let the sync retry. If it keeps failing, the file is stuck in the repository’s history and Lovable Support has to help.
07
The GitHub app was uninstalled or lost access
A workspace owner or admin adds a new connection in Workspace settings, then reconnects each project. Reconnecting doesn’t bring back the old repository: Lovable creates a new one for each project.
Checked against the vendor’s docs on : Lovable docs: GitHub integration.
Rather hand it over?
Fixed scope, fixed price, paid upfront. The work happens in writing; no call needed.
- from $450App Fix TicketOne reproducible bug in an existing mobile or web app, diagnosed and fixed.See scope and start
- from $450AI-Built App RescueA Lovable, Bolt or Cursor app checked end to end in 3 days, then its worst problems fixed at a fixed price.No issues worth fixing, no charge. If the Launch Check finds nothing rated medium or higher, Simon refunds the full $450. You keep the report either way.See scope and start
Related: Hire a Lovable developer · Move Lovable Cloud to your own Supabase · Lovable app blank after publishing