What is GitHub?
GitHub is where the files behind a website or app live online, with every change saved, labelled and easy to undo.
- 4 minute read
- No code needed
- Free to read
A history of every change.
GitHub is a website that stores the files behind a website or app. It keeps a record of every change made to them.
Think of a shared folder that never forgets. Each time someone changes something, GitHub keeps a snapshot of the whole project, with a note saying who changed what and why. If a change goes wrong, you can go back to any earlier snapshot.
The files are usually code, but they don’t have to be. Words, images and settings can all live there too.
You’ll hear the word repository, or repo. It just means one project’s folder on GitHub, with its full history.
Why a business owner should care.
Your website is a business asset. GitHub is where its master copy lives, so it’s worth knowing what that gives you.
- Nothing is lost. Every version is kept, so a bad change is an undo, not a rebuild.
- You can see who changed what. Each change carries a name, a date and a short note.
- Changes are checked before they go live. Someone can review a change before it touches your real website.
- It can stay yours. The account can sit in your business’s name, so the work stays with you if a developer or agency moves on.
An everyday example, all invented
A café asks for its opening hours to change over the holidays. A fortnight later, someone notices the menu page has gone missing.
Because every change was saved, the developer can see exactly which one removed it and put it back in minutes. Nothing has to be rebuilt from memory.
How it works, in four steps.
Every change follows the same short path. It starts on a safe copy, so the live version isn’t touched until the change has been checked.
- You change a file.Fix a typo, swap a photo or add a page.
- It’s saved as a commit.A snapshot of the change with a short note of what changed and why.
- It’s reviewed in a pull request.A page that shows exactly what changed, so someone can check it first.
- It’s merged into the live version.The change joins the main copy, the one your website is built from.
The words you’ll hear
- Commit
- A saved snapshot of a change, with a short note.
- Branch
- A safe copy to work in, so the live version isn’t touched.
- Pull request
- A request to bring a branch’s changes into the main copy, with room for comments.
- Merge
- Accepting the change into the main copy.
You don’t need to use any of this yourself. It just helps to know the words when your developer, or your AI assistant, uses them.
How I use it.
My own sites live in GitHub, including this one. I’m not a developer. I describe the change I want to an AI assistant. It makes the change and GitHub keeps the record.
Every change is saved with a note, so I can always see what changed and step back if something isn’t right. Nothing reaches the live site until I’ve checked a preview of it. That’s what lets me move quickly without worrying about breaking something.
I first worked this way building the systems we use at The Gallery Real Estate, my agency in Sydney. That’s where the approach was proven, before I brought it to The Gallery AI.
Common questions.
Do I need to learn to code to use GitHub?
No. Most business owners never open it. What helps is having the account in your business’s name, so you hold the keys. Your developer or your AI assistant does the work inside it.
Is it free?
GitHub has a free plan, which is plenty for a typical business website. Paid plans add features for larger teams. Check GitHub’s own pricing page for what’s current.
Can anyone see my website’s files?
Only if you choose. A repository can be private, so only the people you invite can see it.
What’s the difference between Git and GitHub?
Git is the tool that records the changes. GitHub is the website that keeps them online and adds the tools for reviewing and sharing. People often use the two names interchangeably.
What happens if my developer leaves?
If the repository is in your business’s account, nothing is lost. The full history stays with you and the next person picks up where the last one left off.
Where does Netlify fit in?
GitHub holds the files. A service like Netlify turns them into the live website and shows you a preview of every change first. There’s a short guide to that too.
What to do next.
If someone builds or looks after your website, ask them two questions. Where do the website’s files live? Whose account are they in? The answers tell you whether your website has a safety net and whether it’s really yours.
Then read how Netlify turns those files into your live website, with a preview of every change before it goes live.
Get the next guide.
Leave your name and email and we’ll send you the next one when it’s ready. One email, no newsletter.
You’re on the list.
We’ll email you when the next guide is ready. Nothing else.