Additional permission + role to allow management of merge requests on protected branches but still deny push

When a branch is protected, you have to be a master to accept merge request.

In my flow here, this is bad because it lets me push to master myself. In our flow here, everything must be done via merge request. I just need to have access to accept merge requests but not push to them. I've never needed access to push to master, but tend to do so because I have access to it (I'm lazy, and disrespectful of my own rules, I have to be forced).

I suggest that there be an additional permission type "Manage Merge Requests". If a role is given this permission, the protected branch cannot be pushed to, but the user within that role can manage merge requests through accepting, closing, etc...

Given that, the existing roles would not work and so an additional role would need to be created, "Manager", pick any name, but the only difference between existing developer permissions is that the "Manager" role has the above said permission.

I'm will to take this on myself, but would like some review before I start, some general acceptance that this would be considered before I work on it.