Why create feature branches?

Question

BlackTom AI · Accepted Answer

You are asked to consider why teams create feature branches.
Option 1: 'Because commits aren't allowed on main' — This is inaccurate in most workflows. There is generally no universal ban on committing to the main branch; many teams allow small, tested commits or require protected main policies, but the core motivation for feature branches is not about restrictions on main but about isolation of work.
Option 2: 'To duplicate work' — This is misleading. Branching is not primarily about duplicating effort; it aims to manage concurrent work without overwriting each other, not to create redundant copies of code.
Option 3: 'To avoid storing work locally' — This ignores the practical purpose of branches. Branches live in the repository and are not a mechanism to skip local storage; developers still have local copies and branches as part of standard workflows.
Option 4: 'To isolate in-progress features from stable code' — This correctly identifies the main purpose of feature branches: keep incomplete or experimental changes separate from the mainline to preserve stability, enable focused testing, and allow parallel development.

CPSC-491-01 Software Engineering (Fall 2025) CPSC 491 Exam 2

Why create feature branches?

查看解析

登录即可查看完整答案

类似问题

Large commits are discouraged because they:

A pull request is used for:

Merge conflicts occur when:

When you hit ‘commit’ in RStudio, your code changes will be visible on Github.

Git is a centralized version control system.

[table] Which documentation helps track project changes? [/table]

Match Git workflow steps to their descriptions: 1: Fork 2: Clone 3: Commit 4: Pull Request

What is one of the main advantages of Git’s distributed nature?

更多留学生实用工具

考试浏览器助手

风格化写作助手

论文查重助手

文献引用助手

课堂转译助手

课堂笔记助手

Quiz搜索助手

学校历年真题

智能刷题助手

智能匹配练习

希望你的学习变得更简单