Error converting content: marked is not a function
#+TITLE: Tech / Scaled Trunk Based Development * Tech / Branch By Abstraction - use it * * * Source: https://trunkbaseddevelopment.com ** Each committer (preferably a pair-programming duo) in this Trunk-Based Development way of working is streaming small commits straight into the trunk (or master) with a pre-integration step of running the build first (which must pass) ** Google does Trunk-Based Development and have 35000 developers and QA automators in that single monorepo trunk ** People who practice the GitHub-flow branching model will feel that this is quite similar, but there is one small difference around where to release from. ** https://trunkbaseddevelopment.com/context/layer_cake.png ** A key facilitating rule is that Trunk-Based Development teams exclusively either release directly from the trunk - see release from trunk, or they make a branch from the trunk specifically for the actual release. See Branch for release. Teams with a higher release cadence do the former, and those with a lower release cadence do the latter. **