Re:When hiring developers, have the candidate read existing ...
by hedora on Saturday April 16, 2022 @12:33PM
(#31053723)
Even better, identify actual problems you are actually encountering, and design a minimal process to solve those problems.
(Automating code quality stuff with linters is a no-brainer though.)
All this means is that you and your team failed to learn anything from the PR process. If simple things like naming or syntax repeatedly come up then you have a style convention but the devs are ignoring it. The very obvious solution to that is to enforce the rules with a linter, and run the linter on a commit or push hook. If the linter fails then the dev can't open the PR until they fix the issues.
If you have process that's only for box checking and not something that's actually providing useful data the you're not using your time well enough. Removing the process is one solution, but it's not a very good one. Making the process useful is significantly better.