In Git, what is a branch and why would you use feature branches?

In Git, what is a branch and why would you use feature branches?

• A. A branch is a backup copy of the repository; feature branches automatically merge.
• B. A branch is a separate line of development. Feature branches isolate work so the main branch remains stable until features are ready.
• C. A branch is a clone of the repository; feature branches reduce disk usage.
• D. A branch is a tag marker; feature branches are for release versions.

Answer: (B)

In Git, a branch is a separate line of development—basically a lightweight pointer to a series of commits that represents work diverging from the main history. Feature branches let you work on a new capability without touching the main branch, so the main line stays stable and deployable while you code, test, and iterate. When the feature is ready, you can merge it back in, bringing the new work in only after it’s been reviewed and integrated, or discard it if needed. This isolation supports safer collaboration, easier testing, and cleaner releases.

It’s not a backup copy that auto-merges, not a clone to save disk space, and not a tag marker for releases. Those ideas don’t capture how branches function as separate development lines that you can merge, revise, or delete as part of normal workflow.