Lesson 10 of 16 · 35 min suggested practice
Sync Lovable with GitHub and keep a recovery plan
Back up the source code, understand two-way sync, and distinguish code portability from moving databases and services.
Connect the intended account and repository
Open the project's Git settings and connect the GitHub account or organization that should own the code. Review the requested repository access and choose the appropriate scope. Link Resource Shelf to its repository, then confirm that the latest project files and a recent change appear there.
Current documentation describes a workspace connection and a project repository link. The shared connection authorizes access; the project link selects the repository. Keep these concepts separate when working across personal, client, or organization accounts so a project does not end up under the wrong owner.
Verify one small round trip
Make a reversible text change in Lovable and confirm it reaches GitHub. Then make a small change on the active synced branch through your usual development workflow and confirm it appears in Lovable. The integration edits and syncs one branch at a time, so inspect the active branch before diagnosing a missing change.
Use this exercise to understand the workflow, not to experiment with secrets or production data. Record a known-good commit after the library's main paths work. For larger changes, use branches and review practices appropriate to your project.
Inventory what exists outside the repository
List public worksheet files, database data, storage buckets, authentication providers, redirect URLs, domains, analytics configuration, and any API integrations. State how each can be recovered or reconfigured. The first static Resource Shelf has fewer moving parts; the optional account version needs a more complete inventory.
Lovable's ownership documentation says created code and content belong to the user subject to third-party rights. That does not remove licenses attached to imported packages, images, fonts, or templates. Record those dependencies when packaging a reusable resource or client handoff.
Check the actual stack before moving hosting
Current documentation distinguishes newer TanStack Start projects from older React and Vite projects. The former can run server code; the latter may build as static files. Inspect your actual project rather than copying a deployment recipe from an older video.
Moving code is one part of a migration. Data, authentication, files, environment configuration, and service calls need their own plan and verification. You do not need to migrate hosting for this lesson; the goal is to know what you own, where it lives, and how you would restore a working copy.
Try this focused prompt.
Create a recovery inventory for Resource Shelf without changing hosting. Identify the actual framework, build commands, runtime, repository and active synced branch, public resource files, database, storage, auth configuration, domains, and external services. Explain which items Git sync preserves and which need separate export or setup. Help verify one harmless two-way GitHub change and record a known-good commit. List third-party licenses that matter when sharing the project.
Replace the sample context with your own approved facts. Review Lovable’s proposed changes before accepting them.
Evidence before the next step
Check your work.
- A harmless change has completed a GitHub round trip.
- The recovery inventory includes non-code dependencies.
- You know the actual framework and hosting requirements.
Your checkmark stays in this browser. It records your own progress, not a certification.
Official sources & further reading
- Sync your Lovable project with GitHub
- Deployment, hosting, and ownership options with Lovable
- Revert and restore your project with version history
Reviewed November 19, 2026. Plans, terminology and interfaces can change; follow the linked documentation if your workspace differs.