I always thought, effectively, commit to master === intent to deploy that code (assuming automated tests pass) If you want to commit unreviewed (or even review

I always thought, effectively, commit to master === intent to deploy that code (assuming automated tests pass) If you want to commit unreviewed (or even reviewed) code to a pre deployment branch, then make it just that, no? Have developers commit to a pre deployment branch and merge accepted PRs from there into master. At some point you have to say “this code is going to trigger deployment”.