Most projects work around this by setting their branches' default reviewers to another team that has a contact address (to prevent the emails from going directly to the members) and the actual team of reviewers as a member (so they still have full review privileges).
Most projects work around this by setting their branches' default reviewers to another team that has a contact address (to prevent the emails from going directly to the members) and the actual team of reviewers as a member (so they still have full review privileges).
For example, branches maintained by the Launchpad team are owned by https:/ /launchpad. net/~canonical- launchpad- branches, but their default reviewer is set to https:/ /launchpad. net/~launchpad- reviewers. ~launchpad- reviewers' mailing list gets the review notifications, and ~canonical- launchpad- branches is a member so its members can review without being spammed.