Glossary · Automation software engineering and architecture
Feature branch
Also known as: Topic branch
German: Feature-Branch
In version control, a feature branch is a branch created to develop a single feature, fix or change in isolation from the main line, which is merged back, usually after review and automated checks, once the work is complete.
- Software engineering
In one sentence
A feature branch isolates work on one feature or fix from the main line until it is reviewed and merged back.
Example
The developer implements the new barcode reader interface on a feature branch; the pull request triggers CI, and a colleague reviews it before merging.
How it applies
- Engineering: Feature branches keep unfinished work out of the main line and provide a natural unit for review. Keep them short-lived; long-running branches diverge and cause painful merges.
- Change control: A feature branch per change request makes it easy to link code changes, reviews and tests to the request, which supports Traceability.
- Documentation: Documentation changes for a feature can be made on the same branch as the code, so both are reviewed and merged together. This docs-as-code approach helps keep manuals and software in step.
Feature branch vs. feature flag
A feature branch hides unfinished work in version control. A Feature flag hides it at runtime, allowing the code to be merged early while the feature stays switched off. Teams practicing trunk-based development often prefer feature flags to long-lived feature branches.