References: Team workflows: GitHub Flow, GitFlow, Trunk-based, Forking
Primary sources
Section titled “Primary sources”Atlassian Git Tutorials, “Comparing workflows” series, the most comprehensive public comparison of git workflows. Licensed under Creative Commons Attribution 2.5 Australia.
- Centralized workflow: atlassian.com/git/tutorials/comparing-workflows
- Feature branch (GitHub Flow): atlassian.com/git/tutorials/comparing-workflows/feature-branch-workflow
- GitFlow: atlassian.com/git/tutorials/comparing-workflows/gitflow-workflow
- Forking: atlassian.com/git/tutorials/comparing-workflows/forking-workflow
Trunk-based Development, the canonical reference at trunkbaseddevelopment.com. The site is the most authoritative source for the workflow’s tenets, anti-patterns, and migration guidance.
GitHub Docs, GitHub Flow at docs.github.com/en/get-started/quickstart/github-flow. Licensed under Creative Commons Attribution 4.0. The original GitHub Flow definition, from the company that invented it.
Vincent Driessen’s original GitFlow article (2010) at nvie.com/posts/a-successful-git-branching-model. The 2010 post that introduced GitFlow. Driessen added a 2020 update note acknowledging that GitFlow isn’t the right choice for many teams, still worth reading as the canonical reference for the model.
Secondary sources
Section titled “Secondary sources”Pro Git by Scott Chacon and Ben Straub. Chapter 5 (Distributed Git) covers contributing-to-a-project workflows. Licensed under Creative Commons Attribution Non Commercial Share Alike 3.0 Unported. Read at git-scm.com/book/en/v2/Distributed-Git-Distributed-Workflows.
Branch protection rules documentation:
- GitHub: docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches
- GitLab: docs.gitlab.com/ee/user/project/protected_branches.html
- Bitbucket: support.atlassian.com/bitbucket-cloud/docs/use-branch-permissions
Further reading
Section titled “Further reading”On CI/CD philosophy: Martin Fowler’s article on Continuous Integration is the canonical explanation of why CI matters and how it pairs with branching strategies. Highly recommended.
On feature flags: Feature Toggles by Pete Hodgson on martinfowler.com covers the taxonomy (release toggles, experiment toggles, ops toggles, permission toggles) and implementation patterns. Useful for teams considering Trunk-based.
On engineering culture and workflow choice: Will Larson’s “An Elegant Puzzle” and “Staff Engineer” books cover how workflow choices interact with team culture at scale. Optional, but useful for engineering leaders making the choice.
On the GitFlow critique: several articles in recent years have criticized GitFlow as outdated. The most cited is GitHub Flow vs. GitFlow which makes the case for GitHub Flow being the modern default.
What this lesson does not cite
Section titled “What this lesson does not cite”L9 does not cite specific company engineering blog posts about workflow choices. Many exist (Spotify, Etsy, Shopify, Stripe), but none has emerged as canonical. The patterns in L9 are the consensus across these sources.
L9 also does not cite specific feature-flag SaaS products (LaunchDarkly, Unleash, Split, etc.). These are tools that implement the feature-flag concept; the concept itself is the load-bearing learning.
License of this lesson
Section titled “License of this lesson”This lesson is part of the Clawdemy curriculum, licensed under Creative Commons Attribution NonCommercial Share Alike 4.0 International. Pro Git’s CC BY-NC-SA 3.0 license and Clawdemy’s CC BY-NC-SA 4.0 license are directly aligned (the 4.0 license is an approved compatible adaptation license for 3.0 source material per the 3.0 license’s later-versions provision). Commercial use is licensed separately at /legal/licensing.