How deeply does Think Like a CTO cover GitHub flow?

Defines the branch sequence and defers naming, lifetime, ticket integration, release cycle, tooling, and reporting to local policy.

GitHub flow

As explained in 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.

GitHub flow is a simplified branching model built around one main branch. Development happens on short-lived feature branches, which are reviewed and tested before merging into the main branch for deployment. section 9.3

Adapt the workflow to the operating context:

Choose branch naming, lifetime, granularity, ticket integration, release cycle, tooling, and reporting practices that fit the team and enterprise. section 9.3
Keep the main branch deployable by reviewing and testing feature branches before merging them. section 9.3

A feature change

A developer branches from the main branch, makes a change, submits the feature branch for review and testing, and merges it into the main branch when it is ready for deployment. section 9.3

How Think Like a CTO covers it

liveBook manning.com

Read Think Like a CTO on liveBook Get the book at manning.com

Also explained in

liveBook manning.com

GitHub Actions in Action: Continuous integration and delivery for DevOpsGitHub Flow is a lightweight branching workflow in which changes are developed on branches, reviewed through pull requests, merged into the main branch, and deployed.

Compare how 2 books explain GitHub flow →

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.

This explainer was generated by Manning's knowledge graph from the text of Think Like a CTO. The section links point to the parts of the book it draws on.