diff --git a/book/05-distributed-git/sections/distributed-workflows.asc b/book/05-distributed-git/sections/distributed-workflows.asc
index 4d0164adb..769c28e51 100644
--- a/book/05-distributed-git/sections/distributed-workflows.asc
+++ b/book/05-distributed-git/sections/distributed-workflows.asc
@@ -83,6 +83,18 @@ image::images/benevolent-dictator.png[Benevolent dictator workflow.]
 This kind of workflow isn't common, but can be useful in very big projects, or in highly hierarchical environments.
 It allows the project leader (the dictator) to delegate much of the work and collect large subsets of code at multiple points before integrating them.
 
+[[_patterns_for_managing_source_code_branches]]
+==== Patterns for Managing Source Code Branches
+
+[NOTE]
+====
+Martin Fowler has made a guide "Patterns for Managing Source Code Branches".
+This guide covers all the common Git workflows, and explains how/when to use them.
+There's also a section comparing high and low integration frequencies.
+
+https://martinfowler.com/articles/branching-patterns.html
+====
+
 ==== Workflows Summary
 
 These are some commonly used workflows that are possible with a distributed system like Git, but you can see that many variations are possible to suit your particular real-world workflow.