Git Flow
Git Flow is a Git branching workflow that organizes development through dedicated branches for features, releases, and fixes.
Infrastructure as Code, Patterns and Practices: With examples in Python and Terraform
Git Flow is a branching workflow that organizes software development around dedicated branches for features, releases, and fixes.
- How it is used
- Organizes concurrent configuration changes into independently reviewable and testable branches before main integration.
- How deep it goes
- Demonstrates cloning, branching, committing, pushing, synchronizing, merging, testing, and conflict reconciliation.
- Examples
- Uses firewall-rule and license-update branches, ticket-based names, Git commands, diffs, and merge output.
- What you can do after
- Apply it via Git to isolate changes, synchronize branches, submit reviews, resolve conflicts, and merge tested work.
Think Like a CTO
A Git branching model with separate master and develop branches and feature branches merged into develop before release.
- How it is used
- Organizes team development and release management through separated integration and deployable branches.
- How deep it goes
- Explains branch roles and merge paths, while deferring naming, lifetime, ticket integration, and release cadence to each environment.
- Examples
- Uses master, develop, and feature branches to illustrate reviewed development and release merges.
- What you can do after
- Apply it via Git by structuring feature work, reviews, integration, and releases across defined branches.
Lead Developer Career Guide
A software development methodology that organizes work in Git through designated branches and branch-based integration practices.
- How it is used
- Organizes Git collaboration and deployment work through designated branches and documented integration practices.
- How deep it goes
- Defines main and development branches, then outlines naming, QA, merging, error handling, and deployment documentation.
- Examples
- Uses main and development branches, feature and hotfix naming, QA, staging validation, production merges, and a deployment chart.
- What you can do after
- Operate/configure it by documenting branch names, validation stages, merge handling, cherry-picking, and deployment steps.
Related concepts
- gituses · Git is a distributed version-control system that records changes to files and supports managing project history and collaboration across repositories.
- branchuses · 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.
- versioning patternkind of · A prescribed arrangement of branches, integrations, releases, and related version-control practices.
- deployment pipelineuses · A sequence of automated or manual stages that builds, tests or validates, packages, and delivers software or models toward deployment.
- GitHub flowalternative to · GitHub Flow is a lightweight Git branching workflow in which changes are developed on branches, reviewed, and merged into a main branch.
- feature-based developmentkind of · Feature-based development is a software and infrastructure workflow that isolates changes on separate branches before review and merging.
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.