Re:Keeping master green at scale
by lozenge on Thursday April 18, 2019 @05:29PM
(#19694968)
Yours seems identical to Bors, just for Gitlab instead of GitHub? That isn't really what's described in the OP.
[ Parent
| on HN ]
Yup, pretty much. I was mostly answering the parent, who in turn was questioning the lack of novelty.
The concept of an evergreen master with testing done in branches, followed by automated merges/rebases is not special. Quite a few companies have been doing it for years, it's the off-the-shelf tooling and subsequent publicity that haven't necessarily been around as long.
As for OP's material? The automated conflict resolution via reordering to optimise parallelism - that certainly feels novel.