How to Connect GitHub to Lovable
Lovable can save your project to GitHub automatically, but the connection lives in your account settings, not inside a single project. Here is exactly where to find it and what each screen actually asks you to click.
Your MissionForge guide lives inside your browser
An overlay appears directly on top of Supabase and Lovable. No tab switching, no re-reading docs.
Copy your Project URL
Find the Project URL field below and click the copy icon. We will use this in Lovable’s environment settings.
Stylized preview. The real guide is interactive, not a screenshot.
Switch to the right project
Open your project switcher first. This is where the menu that leads to your account settings lives.
Open your account menu
From the switcher, open your account menu. Your settings and connections, including GitHub, live in here.
Open Settings
Click Settings to open your project settings, this is where you manage connections like GitHub.
Select the Git tab
Select Git from the settings menu. Git is the system GitHub is built on, so this is the right tab even though the option is not labeled GitHub yet.
Click GitHub
Click GitHub to start syncing your project. This is the actual link between Lovable and your code storage.
Snag: you may be asked to sign into GitHub mid-flow
Clicking Add connection can prompt a GitHub sign-in if you are not already logged in on that browser. That is normal, not an error, sign in and continue.
Click Add connection
Click Add connection to begin linking your GitHub account.
Approve the account
Click Add account to finish connecting GitHub. Pick the account you just signed into and approve it.
This is a one-time setup
Once linked, Lovable saves every future change to GitHub automatically. You will not need to repeat this for new projects tied to the same account.
Why this lives in account settings, not a project
GitHub is connected once, at the account level, rather than switched on separately inside every project. That means the setup you do here carries over automatically the next time you start something new in Lovable, you are not repeating these steps per project.
What the Git tab actually controls
The settings menu groups GitHub under a tab called Git, since GitHub is one implementation of the underlying Git version control system. If you are looking for GitHub specifically and only see Git, that tab is still the right place, GitHub is the option waiting inside it.
Want to build this for real instead of just reading about it?
Frequently asked questions
Where do I actually find the GitHub connection in Lovable?
It is under your account settings, not inside an individual project. Open your project switcher, then your account menu, then Settings, then the Git tab.
Why does the settings menu say Git instead of GitHub?
Git is the underlying version control system GitHub is built on, so Lovable groups the connection under that tab. GitHub is the option you select once you open it.
Do I need to sign into GitHub separately?
Only if you are not already signed in on that browser. Clicking Add connection will prompt a GitHub sign-in first if needed, then let you approve the account.
Do I have to reconnect GitHub for every new Lovable project?
No. The connection is made once at the account level, so new projects can use it without repeating the setup.
What happens after I click Add account?
Once approved, Lovable starts saving changes to GitHub automatically going forward. There is nothing further to configure for that connection.
Is connecting GitHub required to use Lovable?
No, but it is what turns your project into a real, versioned codebase instead of something that only exists inside Lovable's preview, and it is what a deploy step later pulls code from.
Do this before you build much, not after
Since the connection saves everything going forward but does not retroactively fix a project with no history, linking GitHub early gives you a backup from the start.
Use the account you will keep long-term
Since this is an account-level connection reused across projects, sign in with the GitHub account you actually plan to keep using.
Do not panic at the GitHub sign-in prompt
Being asked to sign into GitHub partway through is expected behavior, not a broken connection.
Check the Git tab, not just search for GitHub
If you are scanning the settings menu for the word GitHub, look for Git first, that is the tab it lives inside.
Why people drop off before they finish
You're not the problem. The format is. Here's what changes when you switch to an interactive mission.
- ✕Pause, rewind, pause again, repeatedly
- ✕The UI has changed since recording
- ✕No feedback when you complete a step
- ✕Lose context every time you switch tabs
- ✓Live overlay, no tab switching ever
- ✓Always current: guides track the real UI
- ✓Instant confirmation at every step
- ✓Full context stays open in your browser
Looking for the next thing to build? Browse every mission and find one that matches what you are trying to ship.
Browse all missions