It is insane to me that kernel maintainers do not have build pipelines that automatically run for every PR. The computers should be checking formatting, basic compilation, testing, etc etc.
https://01.org/lkp/documentation/0-day-test-service
https://linux.kernelci.org/job/
"kernel test robot" example email: https://lore.kernel.org/netdev/202102070253.xooT3PWR-lkp@int...
While I firmly believe in "trickle up" economics", I still believe in trickle down productivity investment. It is important to increase the productivity of patch review (CI, etc., done by the experts manually today) before increasing the productivity of patch submission (done by everyone else).
I know it's probably super hard to "unit test" some of this stuff but... does the Linux kernel have effectively 0 testing?
At Linux kernel level you can't effectively have "a CI". Unless you have massive amounts of funds and time to invest of course. I'm sure MS has some complex pre-release automation.