If I understand your post correctly, I agree with its substance: keep unreviewed changes small, probably a subclass of Kanban's "reduce WIP". This should be alr

If I understand your post correctly, I agree with its substance: keep unreviewed changes small, probably a subclass of Kanban's "reduce WIP". This should be already known industry-wide. The Kubernetes Contributor guide states: "break large changes into a logical series of smaller patches which individually make easily understandable changes, and in aggregate solve a broader issue". However, I feel that your technological choice is a bit nitpicking. I believe that creating an alias for 'git checkout master; git pull; git checkout my-branch' and another alias for 'git push; curl .../review' would essentially implement the same workflow as you suggest. (Granted, in some organizations, creating a branch is a heavy process: It requires opening a JIRA ticket, the branch needs to be well-named, etc. but these are not technological issues.)