This article was more interesting than I expected from the title. I was expecting something about how GitHub sells FI to enterprise clients, or what features t

This article was more interesting than I expected from the title. I was expecting something about how GitHub sells FI to enterprise clients, or what features they have to add to FI to make it palatable to enterprises (the latter is touched on a bit). A more informative title would be "How GitHub manages long-lived development branches". Usually long-lived branches mean you're Doing It Wrong (TM), but as the article indicates, enterprise customisation is one case when a long-lived, occasionally-synced branch makes sense; another is maintaining released versions of installed software.