GitHub, demystified

GitHub is just a place that stores your code and tracks every change you make. Three concepts cover 90% of what you need.

Repository (repo)

A folder for your project, stored on GitHub's servers. Your Lovable app is one repo.

Commit

A saved snapshot of your code at a moment in time, with a short message describing what changed. Every time you make meaningful progress, you commit. If something breaks later, you can roll back to any previous commit.

Branch

A parallel copy of your code where you can experiment without breaking the working version. The default branch is usually called *main*. When you want to try something risky, make a new branch, mess with it, and only merge it back to main when it works.

A simple solo workflow

1. Connect your Lovable project to GitHub from the editor. 2. Lovable pushes every change automatically — you don't lift a finger. 3. When you reach a stable version, tag a release in GitHub. That's your safety net. 4. Before risky changes, create a branch. Revert with a few clicks if it breaks. 5. Write commit messages future-you can read. *"Fixed module 4 button"* beats *"updates"*.

You don't need pull requests, rebases, or any developer-team ceremony. Commit often, tag stable versions, branch before risky changes.