Hacker News Reader

This would be true if we had one person responsible for the merge! We have a small team of developers and proper rebase and merge is the responsibility of the PR author after it has passed code review + testing.

In short: all devs are admins.

edit: anyway this would still be a huge help to the sole admin if we had one.

Because sometimes the admin just tells you "ok, rebase then I will merge" and don't bother doing the rebase himself...

If there is a conflict during the rebase, the developer working on the new feature will have more information on how to fix it. So it makes sense for the developer to rebase before submitting.

Why would you have a separate "admin" do that? It doesn't require a separate skillset; the developer is in the best position to shepherd their feature into production, and by giving them ownership of their feature they can stick closer to solving the actual problem, and likely get more satisfaction from their work as well.