I agree with this in principle, BUT... be reasonable, and don't go in thinking you have to "show this guy" or communicate to the team what a hardass you are. Th

I agree with this in principle, BUT... be reasonable, and don't go in thinking you have to "show this guy" or communicate to the team what a hardass you are. There are, in my experience, always exceptions to pretty much any policy. If you say "all commits need the PR workflow" I'd posit that that really means "for actual application code that ultimately winds up released" and nothing more. If you now try to apply that policy to every random repo with some POC, demo, experiment, or throwaway code of some sort, you're just going to piss people off needlessly. So work with the team to figure out what repos actually need this policy applied, don't just apply it blindly. Similar reasoning could be applied to most other things. Don't just go issuing wide-ranging edicts because you can, without understanding the actual downstream impact.