Why isn't GitHub syncing with Lovable?
Last checked 31 Aug 2026
Short answer
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.
Common causes
- Authorisation revoked or expired. If the Lovable GitHub App was uninstalled, or access was revoked in GitHub's settings, sync silently stops.
- Repository permissions changed. If the repo was made private/moved/renamed, or org policies changed which apps can access it, sync can break.
- Branch protection rules. If the target branch requires pull request reviews or has other protection rules, Lovable's automatic commits may be blocked from pushing directly.
- Conflicting simultaneous edits. Editing the same files in Lovable and directly in GitHub (or a local clone) around the same time can create conflicts that stall sync until resolved.
- Temporary connectivity/service issue on either GitHub's or Lovable's side.
How to fix it
- Check GitHub → Settings → Applications (or Organization settings → Installed GitHub Apps) to confirm the Lovable app is still installed and has access to the repo.
- In Lovable's project settings, check the GitHub/Git sync connection status — reconnect if it shows disconnected or errored.
- Check whether the target branch has protection rules that block direct pushes; adjust them if you want automatic sync to keep working.
- Look at the repository's commit history to see the last successful sync, which narrows down when it stopped.
Check the GitHub sync status for this project and tell me if the connection needs reauthorising.
What usually goes wrong
- Someone with repo admin access removes or downgrades the Lovable app's permissions without realising it breaks sync.
- A branch protection rule added for good reasons (e.g. requiring PR reviews) unintentionally blocks Lovable's automated commits.
- Assuming it's a Lovable bug when the cause is on the GitHub organisation's permission settings.
If reconnecting doesn't resolve it, Lovable's support/help resources are the next step — see /help.
Sources
Was this answer helpful?
Related questions
- AnswerHow 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.
- AnswerCan 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).
- AnswerDoes 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.
- AnswerCan I edit Lovable code directly in GitHub?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.
