> Isn't this why we have CI/CD and scheduled pipelines? I mean, kind-of. One of the problems with CI/CD though is that they're poorly designed for the job th

> Isn't this why we have CI/CD and scheduled pipelines? I mean, kind-of. One of the problems with CI/CD though is that they're poorly designed for the job they do; see this: http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.26.2533&rep=rep1&type=pdf http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.26.... The TL;DR here is that by structuring your code and storing it in a database structured hierarchically you can solve CI/CD in a MUCH nicer manner: your root node's history becoming a history of the project in a compilable state.