GitHub flow
GitHub Flow is a lightweight Git branching workflow in which changes are developed on branches, reviewed, and merged into a main branch.
Think Like a CTO
A simplified Git branching model centered on a main branch and short-lived feature branches that are reviewed, tested, and merged for deployment.
- How it is used
- Uses one deployable main branch to organize reviewed, tested development and deployment.
- How deep it goes
- Defines the branch sequence and defers naming, lifetime, ticket integration, release cycle, tooling, and reporting to local policy.
- Examples
- Demonstrates branching from the main branch, reviewing and testing changes, and merging them for deployment.
- What you can do after
- Operate/configure a branching workflow by selecting suitable branch, review, release, tooling, and reporting practices.
GitHub Actions in Action: Continuous integration and delivery for DevOps
GitHub Flow is a lightweight branching workflow in which changes are developed on branches, reviewed through pull requests, merged into the main branch, and deployed.
- How it is used
- Organizes continuous-integration and delivery work around feature branches, pull requests, protected main, and deployment.
- How deep it goes
- Explains branch, review, protection, merge, and trigger stages, while deferring detailed action-workflow implementation to surrounding workflows.
- Examples
- Uses feature/name-of-feature branches, pull requests, compilation checks, security checks, container registries, and versioned releases.
- What you can do after
- Operate a reviewed branching workflow that produces deployable main-branch changes and staged release artifacts.
Related concepts
- 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.
- pull requestuses · A pull request is a version-control proposal to integrate changes from one branch or repository into another, typically supporting review and discussion before merging.
- trunk-based developmentalternative to · 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.
- code reviewuses · Code review is the systematic examination of source code or proposed changes to identify problems and assess or improve quality.
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.