Earlier quoted context omitted.
We have emergency production rollback to the last working deploy. That's what you do when breaking changes are committed to master. Letting devs commit to master directly? Horrible idea.
That’s a great strategy that works in some scenarios. Preventing weekend breaks would depend on a daily deploy schedule? I do normally revert first and ask questions later when breaking changes appear, that’s similar to what you’re saying, I think... > Letting devs commit to master directly? Horrible idea. I’ve never been on a team that disallows commits to master. I can see the thinking, and maybe I should be doing…
I'd be more concerned about code being committed to master without code review.