A tiny question: does this mean a workflow in which only one user would be able to merge a specific branch (say: master) is only available in the enterprise edition? I imagine this is quite a common workflow, even at smaller companies or non-profits. This essentially forces you to use an entire repo per user to do code review, even though oftentimes you wouldn't need this when you can restrict branch access to a specific (set of) users.

For example, I'm active at a small non-profit computer shop at the campus of my university, and we develop our own stock managementsystem inhouse. This would be a very interesting feature even for non-enterprise users like us, because that'd allow for easy code reviews without having to fork the repo.