Chapter 14. Recommended team workflows
This chapter covers
- Using GitHub Flow to manage an untagged project
- Using Git Flow to manage a tagged project
- Using Mike Flow Single to manage a single-release project
- Using Mike Flow Multiple to manage a multiple-release project
You saw in sections 13.1 and 13.2 that two teams can both use Git as a version control system to manage a software project but handle branches, merging, and rebasing very differently. The different strategies for deciding how and when to branch, merge, or rebase as part of a team are called team workflows. These workflows allow for different ways of handling (or not handling) stable releases, tags, and bug fixing of previous releases. In this chapter, you’ll learn about ...
Get Git in Practice now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
