@roti yeah I protected the master branch so that changes are unit tested before being merged to master. You followed the right workflow by creating a branch then submitting a PR, but if that's too onerous and/or we are still at a point where it makes more sense to live dangerously, I'd be open to unprotecting master.

Thoughts?

That's fine with me. The only drawback is that we'll have a lot of branches, but if we clean them up then it should be fine.

Yeah. Thankfully upon merging a branch, GitHub offers the option to delete the branch right then & there (and I make extensive use of that feature). It won't clean up branches in clones obviously, but at least the central repo stays clean.