Branch
A branch is an independently evolving line of development in a version-control repository, typically represented by a reference to a sequence of changes or commits.
Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform
A branch is a named line of development in a version-control repository that maintains changes independently from other lines until they are combined.
- How it is used
- Uses branches to isolate infrastructure changes, coordinate teammates, and control how emergency or feature changes reach production.
- How deep it goes
- Defines branches and demonstrates creation, committing, pushing, updating, merging, testing, and conflict reconciliation.
- Examples
- Uses firewall rules, license updates, emergency module fixes, and operating-system image rollbacks as concrete cases.
- What you can do after
- Apply it via Git to isolate, commit, publish, update, test, and merge infrastructure changes.
Building User-Friendly DSLs
A named sequence of version-control commits representing an independent line of work.
- How it is used
- Supports concurrent, reviewable, and asynchronous development of features or bug fixes.
- How deep it goes
- Defines branches within distributed version control and explains branching, commits, review, merging, and merge conflicts.
- Examples
- Uses main, feature, and bug-fixing branches as naming examples, alongside commit sequences and merge-conflict scenarios.
- What you can do after
- Operate Git-based distributed workflows by isolating changes, sharing commits, reviewing work, and merging branches.
Contract Testing in Action
A branch is a named line of development used to associate Pact artifacts with a particular development stream.
- How it is used
- Associates Pact contracts and verifications with Git development streams in pull-request and CI/CD workflows.
- How deep it goes
- Explains branch creation during publication and verification, environment configuration, selectors, and automated workflow testing.
- Examples
- Uses WebConsumer and MoviesAPI contracts, GitHub Actions variables, package.json scripts, and GraphQL workflow exercises.
- What you can do after
- Operate/configure Pact publication and verification so providers select contracts from matching and main branches.
Practical Automation with PowerShell: Effective scripting from the console to the cloud
A branch is a named line of development in a version-control repository containing its own sequence of changes.
- How it is used
- Supports safe team development by isolating changes from the main codebase until they are tested and reviewed.
- How deep it goes
- Explains branch creation, synchronization, commits, pushes, pull requests, conflicts, merging, and cleanup, while deferring advanced checks.
- Examples
- Demonstrates a develop branch, a module version update, GitHub synchronization, and a pull request reviewed through file differences.
- What you can do after
- Apply it via Git, GitHub CLI, and the GitHub browser to isolate, publish, review, merge, and remove development work.
Think Like a CTO
A named line of development in a version-control repository that can diverge from and later be integrated with another line.
- How it is used
- Organizes development work so teams can segregate commits, review changes, and control integration and release flow.
- How deep it goes
- Explains branch-count trade-offs and workflow policies, but stops short of implementation details.
- Examples
- Compares Gitflow’s master/develop structure with GitHub flow’s single-master structure and feature branches.
- What you can do after
- Operate/configure branch workflows by selecting branch structure, naming, lifetime, review, integration, and release rules.
Statistics Every Programmer Needs
A branch is an edge in a decision tree representing one possible outcome of a node's test.
- How it is used
- Represents one outcome path from a decision or feature test toward a subsequent node, leaf, probability, payoff, or prediction.
- How deep it goes
- Distinguishes branches in decision-process and machine-learning trees, but does not develop splitting algorithms or branch-selection criteria.
- Examples
- Uses investment alternatives, economic conditions, and home-loan approval based on age and income.
- What you can do after
- Evaluate/understand decision-tree paths by tracing test outcomes to predictions, approvals, payoffs, or other endpoints.
Read how Statistics Every Programmer Needs explains branch →
Related concepts
- trunk-based developmentused by · Trunk-based development is a software workflow in which developers frequently integrate small changes into a shared mainline, typically using short-lived or no feature branches.
- GitHub flowused by · GitHub Flow is a lightweight Git branching workflow in which changes are developed on branches, reviewed, and merged into a main branch.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.