What is a git branch and why you split work into branches

What is a git branch and why you split work into branches

A branch is a separate line of history where you can make changes without touching the stable code.

What it is

A Git branch is a separate path of work inside the same repository. main holds the stable version, and the branch holds the changes for one task.

When the task is ready, the branch can be merged back. If it fails, the main line stays safe.

Why it matters

A branch gives you three things:

• risk isolation;
• parallel work for multiple people;
• cleaner review, because the branch shows only one logical change.

How to work with it

Typical flow:

git switch -c feature/login-validation
# older style:
# git checkout -b feature/login-validation

git status
git add .
git commit -m "Add login validation"
git push -u origin feature/login-validation

What to avoid

• do not work in main for too long;
• do not use random names like temp2 or fix-stuff;
• do not keep one branch for a week without syncing from main;
• do not mix three different tasks into one branch.

Conclusion

A branch is not extra ceremony. It is how you avoid breaking live code while you work.

In simple words

branch = “a separate place for one task so I do not touch the main version.”