Mainline, Feature Branching, Continuous Integration, Release Branch and a clutch of other handy patterns.
https://martinfowler.com/articles/branching-patterns.html
* integration * path to production * Semantic Conflict * point out this flaw * Mainline * Self Testing Code * Deployment Pipeline * Unit Tests * we need to keep the internal quality of the code high * Pre-Integration Review * Self Testing Code * refactor * Diff Debugging * Mainline Integration * Self Testing Code * Healthy Branch * Pre-Integration Review * Collaboration Branch * State Of Dev Ops Report * "if it hurts… do it more often" * Move Statements to Callers * Self Testing Code * Diff Debugging * detailed article * the book * trunkbaseddevelopment.com * "everyone commits to the mainline every day" * Keystone Interface * Semantic Diffusion * feature flags * Self Testing Code * Test Driven Development * Feature Branching * Frequency Reduces Difficulty * as I explained above * Extreme Programming * State Of Dev Ops Report * Pull Requests * Feature Branching * Pre-Integration Review * Mainline Integration * Feature Branching * Continuous Integration * follows this approach * -- Camille Fournier * Pair Programming * Extreme Programming * Refinement Code Review * Continuous Delivery * Healthy Branch * Deployment Pipelines * favor creating the commits on mainline * puts it * integration friction * Environment Branch * long-lived release branch * Deployment Pipeline * Release Branch * Feature Branching * Agile Release Train * Release-Ready Mainline * Continuous Integration * Source Branching * Bodart's Law * LeRoy's Illustration * Continuous Integration * Software Configuration Management Patterns * Software Configuration Management Patterns