Branches and Team Workflow

Branches and merging

Work on independent lines of development.

8 minutes - Absolute beginner

What this means

A branch is a movable name pointing to a commit. Merging combines histories when work is ready.

In beginner terms, this topic answers one practical question: "What should I write, and why does React care about it?" Do not try to memorize the syntax first. First understand the idea, then connect the syntax to that idea.

Why it matters

Feature branches isolate unfinished work from stable branches.

When you build real React screens, this idea helps you decide where data should live, what the user should see, and what should happen after an interaction. That is why this lesson is part of the main path instead of being an optional detail.

Step by step

1. Notice the UI problem this topic solves. 2. Look at the smallest possible example. 3. Change one value and predict what should appear. 4. Run the example and compare the result with your prediction. 5. Use the practice task before moving on.

Small example

git switch -c feature/quiz
git merge feature/quiz

Common mistake

Do not copy branches and merging syntax without explaining what problem it solves and checking the result.

Practice task

Change one part of the example, predict the result, run it, and explain the result in your own words.

Remember this

Keep branches focused and short-lived.

try.it

Examples

Try it: Branches and merging

Edit this focused Git example and run it in the browser preview.

Preview runs browser-safe JavaScript in a sandboxed frame, never on the server.

javascript

editor

preview

Preparing preview...

practice.next

Practice before moving on

check.understanding

Lesson quiz

Login to save progress

You can read lessons without an account, but progress requires login.

Login