We're open-sourcing a setup which has been reviewing all our PRs for many months now as part of our CI. It's been working great for us. Happy to answer any questions!
No, it's full of bugs and missing features, just look at the trackers. It is not, and unlikely never will be, a replacement. It doesn't even support concurrency yet.
I will never, Postgres proper is maintained by many people who know what's in the code. I have no interest in millions of lines generated by one person who has no idea what's in there. It would be irresponsible to downstream users to put them and their data at risk.
Have you tried it, or did you think the question was a good quip? I suspect the later because you aren't familiar with the issues it contains.
4 comments
[ 0.23 ms ] story [ 9.7 ms ] threadWe have something like this, but it's a single directory with less than a dozen files (plus a simple helm chart), why is there so much code?
With almost 2000 commits and 1M LoC changes in the last month, how do you know what's in there?
I will never, Postgres proper is maintained by many people who know what's in the code. I have no interest in millions of lines generated by one person who has no idea what's in there. It would be irresponsible to downstream users to put them and their data at risk.
Have you tried it, or did you think the question was a good quip? I suspect the later because you aren't familiar with the issues it contains.