Git and GitHub Basics for Your AI-Built Project

AI Build South Africa

A fundamentals guide, covering only what a vibe-coder actually needs to know about Git and GitHub, not a general developer course.

Quick answer

Git tracks every change to your project as a snapshot you can return to; GitHub is the website where those snapshots live online, outside your builder platform entirely. You rarely need to type a Git command directly: Lovable and Bolt.new both offer a one-click Connect to GitHub that handles this for you, and Base44 does too, but only from its Builder plan and above. Once connected, GitHub becomes a more precise safety net than your builder's own revert button, since every pushed change is its own inspectable snapshot, not a single remembered "last working version."

Tools for this build

Custom Prompt Builder

Turns your task, in your own words, into a prompt with clear limits for your AI coding agent.

PayFast Webhook Generator

Once your build works and needs a South African payment gateway.

POPIA Compliance Checker

For when your build starts collecting real visitor data.

Git, in one sentence

Git records a snapshot of your project every time you save a meaningful change (a "commit"), and keeps every past snapshot around so you can look at, compare or return to any of them later. This site's own guide to what Git actually is covers that in full, including why it's a separate thing from GitHub, not another name for the same tool; this page assumes it and covers connecting your specific platform.

What GitHub actually adds

GitHub takes that history of snapshots and hosts a copy of it online, at a real, shareable address, outside your builder's own systems entirely. That's the whole function: a genuine backup that exists independently of Lovable, Bolt.new or Base44 staying online or your account staying active on any one of them, plus a way to actually look at your project's history in a browser rather than needing specialised tools to read it.

Worth naming directly: your builder platform already has its own internal version history, the same one this site's guide to breaking vibe-code loops covers using to revert a bad change. GitHub isn't replacing that, it's a second, independent copy sitting outside the platform entirely. If your builder account were ever lost, suspended or simply retired the product, a connected GitHub repository is the one place your project's actual history would still exist.

Connecting your specific platform

Lovable syncs two-way: push a change from Lovable and it appears in your GitHub repository automatically, and a change made directly in the repository pulls back into Lovable the same way. Bolt.new offers both a direct ZIP download and a Connect to GitHub button in its toolbar that pushes straight to a new repository. Base44 supports GitHub sync too, but only from the Builder plan upward.

None of these connections need you to already have a repository set up and waiting; each platform's own Connect to GitHub flow creates one for you as part of the process, on your own GitHub account. The one thing worth doing beforehand is simply having a free GitHub account ready, since every platform's flow asks you to sign in and authorise the connection as its first step.

GitHub support, by platform

Lovable

Two-way sync, every plan:

Push and pull, changes flow both ways

Bolt.new

Connect to GitHub or ZIP download, every plan:

One-click push, no paid tier needed

Base44

GitHub sync, Builder plan and above only:

Free/Starter tiers don't include it

AI Build · aibuild.co.za

Why this matters more than it looks like it should

This site's own guide to breaking vibe-code loops covers using your builder's revert feature to escape a fix-one-break-another cycle, and that feature works well for exactly what it's built for. GitHub, once connected, gives you something more precise: every pushed change is its own separate, inspectable commit, not a single remembered checkpoint. When a specific change three or four prompts back turns out to be the actual problem, a real commit history lets you look at exactly what changed in that one step and return to precisely that point, rather than the single most-recent working state your builder's own revert typically offers.

The five things worth actually knowing

You'll rarely type these yourself if your builder's own GitHub button handles the connection, but recognising them helps when reading a project's history or a guide that assumes you know them: a commit is one saved snapshot with a short message describing it, a push sends your local changes to GitHub, a pull brings changes from GitHub back down, a branch is a separate parallel line of changes you can experiment on without touching your main project and a repository (or "repo") is the project itself, the whole history in one place.

Where to go next

The concept this page assumes: What Is Git?
Stuck in a fix-one-break-another loop right now: Breaking Vibe-Code Loops.
Still choosing a tool, and whether its code can leave it: How to Choose a Vibe Coding Tool.

Not affiliated with the platforms we write about

AI Build South Africa is an independent resource. We're not endorsed by, or an official partner of, Lovable, Base44, Bolt.new or GitHub. We do participate in affiliate and referral programmes with some of these providers, including Base44. See our Disclaimer for the full disclosure and our Terms of Service for the wider terms.

Frequently asked questions

Do I need to learn Git if my builder already has "Connect to GitHub"?

Not to get the benefit, since clicking Connect to GitHub does the actual work for you. Knowing roughly what a commit is and how to look at your project's history on GitHub's own site still helps once something breaks and you need to understand what changed, even if you never type a Git command yourself.

What's the actual difference between Git and GitHub?

Git is the underlying system that tracks changes to your project as a series of snapshots, and it works entirely on your own machine or inside your builder, with or without the internet. GitHub is a website that hosts a copy of that history online, so it exists outside your builder platform and can be shared, backed up or viewed from anywhere.

Does connecting GitHub cost anything extra?

A personal GitHub account and a private repository are both free. The cost, where one exists, comes from your builder platform's own plan, not from GitHub itself: Base44 restricts its GitHub integration to the Builder plan and above, while Lovable and Bolt.new both offer it without an extra paid tier.

Can I use GitHub as a backup even if I never type a Git command myself?

Yes. Once your project is connected, every change your builder pushes creates a real snapshot on GitHub automatically, a genuine copy of your project outside the builder's own systems, without you ever opening a terminal or typing a command.

Is Base44's GitHub integration really only on paid plans?

Per Base44's own plan structure, yes, GitHub sync is restricted to the Builder plan and above.

What happens if I mess something up? Does GitHub actually save me?

Yes, more precisely than your builder's own revert button can. Every pushed change is its own commit you can inspect and return to individually, rather than a single "last working version" your platform remembers, which matters most exactly when you're trying to recover from a specific bad change buried a few prompts back.