> I thought it was a neat article I think the article talks about the "What" part of the problem, but the actual code is much more interesting in the "How" sen

> I thought it was a neat article I think the article talks about the "What" part of the problem, but the actual code is much more interesting in the "How" sense. Like the git-ref stuff makes sense as you read the code https://github.com/ligurio/git-test/blob/master/bin/git-test#L466 https://github.com/ligurio/git-test/blob/master/bin/git-test... There was a similar set of additions to svn in the past with "svn propedit" in the workflows which I used in a previous workplace. It was not pretty, because it was like embedding JIRA into svn - but it meant machines could flip state to state with commits during build+test and restart from that point without an independent DB to track the "current state" & people with commit access could nudge a stuck build out without losing "who did what".