We are using microservices(read a lot of GIT repositories) and our department has 90+ java developers. All of them write code which mean there are a lot of PR`s every day. We are using BitBucket and Also we have a self written bot that listen BB events and can sends a PR review notification to slack.
Notify every developers about each created PR looks like PR DDOS. So we configure bot to use two groups: mandatory approvers(PR can't be merge without their approve) and others. There were about 15 mandatory approvers. In this case each PR has to be approved by 1 mandatory and 3 other reviewers to be merged. But daily amount of PR's is too big and mandatory approvers still got a lot of notifications which stops their main work. It was our first approach and we decided to declined it.
The second approach is to split all developers by groups(15-20 devs per group) within related business area and don't use mandatory approvers. In this case each PR has to be approved by five reviewers. After that it's ready to merge. Also such attempt should increase overall expertise cause devs from one business are can review PR more thoroughly.
Right now bot is sending notification to all participant from group to which author belongs. It spread load to all devs from group. The amount of PR's to review changes day by day but usually it is still quietly big.
Maybe there are another approaches use in your company. Just curios to know. Maybe you have some ideas how to rebuild review process.
One of the next steps we are thinking about is to decrease the number of devs in one group which decrease daily amount of PR's for one dev.