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)

Branches in Git are separate lines of development. They’re lightweight pointers to commits that let you work on something new without touching the main branch. Feature branches are created to implement a new feature or experiment in isolation. While you build and test the feature, the main branch stays stable, which helps you ship reliable code and keeps production-ready state intact. When the work is ready, you merge the feature branch back into the main branch after review and testing, resolving any conflicts along the way. This approach enables parallel work by multiple developers, makes continuous integration smoother, and gives you a clear point to revert if the feature needs to be dropped. It's not a backup copy, not a clone, and not a tag marker—it's a separate development line designed to keep changes organized and controllable.

Branches in Git are separate lines of development. They’re lightweight pointers to commits that let you work on something new without touching the main branch. Feature branches are created to implement a new feature or experiment in isolation. While you build and test the feature, the main branch stays stable, which helps you ship reliable code and keeps production-ready state intact. When the work is ready, you merge the feature branch back into the main branch after review and testing, resolving any conflicts along the way. This approach enables parallel work by multiple developers, makes continuous integration smoother, and gives you a clear point to revert if the feature needs to be dropped. It's not a backup copy, not a clone, and not a tag marker—it's a separate development line designed to keep changes organized and controllable.