What GitHub stores
GitHub is a service for keeping code in a repository — a project folder with change history. A commit is a recorded set of changes, like a labeled checkpoint. The supported Lovable GitHub connection can sync project code with a repository. Check the current connection steps and permissions before authorizing it. GitHub is not automatically your public hosting service, and a repository address is not the same as your visitor website address.
Connect only an account you control
Use an account and repository appropriate for your business. Review which repositories the connection may access. Confirm the repository's public or private visibility; private business material should not become public accidentally. Protect the account with two-factor authentication — an extra sign-in check beyond a password. Do not rename, move, disconnect, or delete a connected repository without reading current guidance because the sync connection can be affected.
Code history is not a whole-site backup
A repository usually contains the code and files actually committed to it. It does not automatically contain live database records, all media uploads, secrets, DNS settings, payment accounts, or email-service setup. Some assets may be referenced from another service rather than stored in the code folder. Make a backup list by location: code, approved original images, stored records, and service settings. Keep private exports protected, not in a public repository.
Understand portability
Portability means how easily you can move your site elsewhere. Having source code can help, but a different host may need build settings, runtime support — the environment that executes the site — secrets, database connections, and replacement services. A successful code download does not prove the site will work on another host. Vercel, Netlify, or Cloudflare may suit some setups; verify compatibility for your actual project. Traditional builders and Shopify have their own export limits, and a Shopify theme is not a portable standalone store.
GitHub Pages has limits
GitHub Pages hosts static sites — pages delivered as files, without a private backend running there. That can suit a simple information site. It is not the full home for a secure customer database, private sign-in logic, or payment processing. Its current usage terms also limit some commercial uses. Do not treat it as the automatic free destination for any business app; check official rules and your site's needs first.
Practice recovery before you need it
Ask what restoring an earlier code version will and will not restore. Keep a record of the required services without writing secret values into ordinary notes. If you export data, check who can access the copy and how long to retain it. Test recovery in a safe separate setup with qualified help when necessary. A backup is useful only when you know what it includes and can restore what matters.
Example prompts to copy and adapt
Replace [BRACKETS] with approved details. Use pretend information for practice, never passwords or customer records.
Backup inventory
Explain this project's GitHub connection and list what is in the repository versus stored elsewhere: code, uploaded media, database records, service settings, and secrets. Do not print secret values. Describe separate backup/recovery steps and what moving to a different host would require. Do not connect, move, delete, or change anything yet.
A real-world example
A cleaner's page code is on GitHub, but quote requests are stored elsewhere. Restoring the Home page cannot recover deleted requests. The owner needs a separate plan for those records, original photos, email setup, and the domain account.
Steps to take
- Locate the current GitHub connection instructions and read the permission request.
- Make a two-column list: code history and separate backups.
- Confirm repository visibility before sharing a link.
- Exercise: explain why downloading code does not restore customer messages or payment settings.
Backup understanding check
This checklist is optional and not saved. Copy it to keep a personal note. Do not enter sensitive information.
Go deeper in related modules
Not sure what a word means? Check Business Words Made Simple.
Official provider guides
Independent resources, not P.E.A.C.E. partners or recommendations. Check current terms before buying.
- Connect Lovable with GitHub (opens in a new tab)
Read current sync behavior, permissions, and connection limitations.
- GitHub Pages limits (opens in a new tab)
Check official hosting restrictions before selecting GitHub Pages.