|
|
|
|
|
by newnewpdro
2732 days ago
|
|
Wouldn't you simply enforce this with automation if you were making a serious effort? It's already quite common for github PR's to require myriad CI tests to pass before anything can be merged... those can incorporate static analysis and warnings as errors. |
|
Try to be that clever guy putting such gates into place without having the team be on the same wave length.
Github is a bubble, there are tons of software projects out there, using a myriad of build infrastructures, or even just doing plain old IDE builds (yes I know, but it is as it is).