GitHub Sync

Example workflows

Starting points built from this record, not transcripts of a run. Each prompt is written the way it should be sent, as one paragraph, and each is worth editing before you send it.

1. 01

   Stand it up from scratch

   You have read the record and want GitHub Sync working in a real project rather than a sandbox.

   Set up GitHub Sync in this project — two-way GitHub sync with branch switching and co-author commits. Walk it end to end, tell me exactly what you changed, and flag anything I have to switch on myself before it works.

   Expected outcome

   A working setup, a plain list of what changed, and a short list of anything left for you to switch on. Check that list before assuming it is done.

2. 02

   Hand-off to a human dev team mid-project

   The record lists this as one of the jobs GitHub Sync is meant for, so it is a fair first test of whether it fits your app.

   In this project, use GitHub Sync for hand-off to a human dev team mid-project. Build the smallest version that a real user could complete end to end, keep the change scoped to that path, and tell me how to test it myself.

   Expected outcome

   One complete path a user can walk, the files and settings that changed, and the steps to test it. Walk it yourself before you ship it.

3. 03

   Review it before you publish

   GitHub Sync is wired in and you are about to put it in front of people. This is the pass that catches the half-configured version.

   Review how this project uses GitHub Sync before I publish. Check two-way sync (push/pull) and branch switching from the editor, list anything that is missing, misconfigured, or only half wired, fix what is safe to fix, and tell me what you left alone and why.

   Expected outcome

   A findings list split into what was fixed and what was left, with a reason for each. Anything left alone is yours to decide on.

4. 04

   Wire up Vercel/Netlify deploy previews

   A second job the record lists for GitHub Sync, useful once the first path works.

   Extend this project so GitHub Sync also covers wire up Vercel/Netlify deploy previews. Reuse what is already wired rather than adding a parallel setup, and tell me what you reused and what is new.

   Expected outcome

   A second path built on the same setup, plus a note on what was shared and what was added.

Frequently asked

• What is GitHub Sync?

  GitHub Sync is Lovable's Integrations feature: Two-way GitHub sync with branch switching and co-author commits. Bi-directional sync between Lovable and GitHub.

• Is GitHub Sync GA or in beta?

  GitHub Sync is generally available (GA) on Lovable.

• What Lovable plan includes GitHub Sync?

  GitHub Sync is available on all Lovable plans.

• When did GitHub Sync launch?

  GitHub Sync launched on Dec 1, 2024.

• Supabase (Native Integration)Same category, also GA · Nov 2024
• Lovable APISame category, also GA · Jan 2025
• Lovable ChatGPT AppSame category, also GA · Dec 2025