Explained Simply — For Beginners
Finished Episode 15? You can upload and Sync. This episode explains why teams use branches — your own safe copy of the project.
Suppose your team has one official document. If everyone edits the same file at the same time, things go wrong fast.
Work on your copy. Merge back only when it’s ready.
Click Next — see the problem with one shared file
A Git branch is exactly that: your own working copy of the project.
Think of the main branch as the official version of a project. A branch is your personal workspace where you can work freely, save progress, collaborate with teammates, and only publish your changes when they’re complete and reviewed.
You don’t create a branch to look “technical.” You create one so your work stays safe, clear, and shareable.
A branch gives you your own workspace. You can make changes without affecting the main project.
Think of it as your own draft before publishing.
A task may take several days. You might finish only 30% today. Without a branch you’d leave main half-finished — or avoid saving.
With a branch, save progress often while main stays stable.
You’re halfway through one task — say updating a landing-page draft. Before you finish, someone asks you to change copy on another page. Your current branch keeps that unfinished work safe.
Save (commit) this branch, switch to a new branch for the other page, then come back later — right where you left off.
You started a feature — now a teammate needs to help. They can check out your branch, continue the work, and push their changes.
Multiple people can share one branch before it’s merged.
You don’t have to wait until the task is “done” to push. Commit and push your branch whenever you want.
The main branch should stay tested and ready. Branches
let you experiment without risking that stable copy.
If something goes wrong, fix — or even discard — only the branch.
Map Git words to drafting a report — same meanings, plain language.
mainClick Next to reveal each pair
A branch is your personal workspace where you can safely develop, save, experiment, and collaborate without affecting the main project until your work is ready.
1. A Git branch is closest to…
2. Why keep incomplete work on a branch instead of main?
3. “Push” on a branch is like…
4. Before you switch to another branch for a different task, you should…