What is a Git branch and when should you create one?
PICTURE THIS: GIT FLOW
Simple meaning
A branch is a movable pointer to a commit, usually used to isolate a feature or bug fix.
WHY — Git instead of guessing?
Why interviewers care about Git:
who only read docs from people who shipped.
and tied to Full Stack work.
Name the idea, why it exists, then one short example.
End with when you use it and one common pitfall.
STEPS — What happens step by step?
Before you speak the answer, walk the interviewer through these steps:
- 1A branch is a
movable pointer to a commit, usually used to isolate a feature or bug fix.
- 2You create one so
main stays shippable while you experiment.
- 3After review you merge
or rebase so the team shares one history of completed work.
- 4Give an example
One tiny concrete case you can say aloud.
- 5Common mistake
What juniors usually get wrong.
- 6Close
When you pick this over the alternative.
EXAMPLE — See it in action
Here's a short line you can speak, broken into clear beats:
Note: Adapt this scaffold to your own project — keep it under 60–90 seconds.
Key takeaway
A branch is a movable pointer to a commit, usually used to isolate a feature or bug fix. You create one so main stays shippable while you experiment.