Team being removed as a Pull Request reviewer after one member has reviewed


We have applied a CODEOWNERS file to our code, which contains the name of a team, in the following format.

* @Org-Name/Team-Name

We’ve also given that team write permissions to the repository, ensuring that the team is added as a reviewer when a Pull Request is created.

When a Pull Request is created, every member of the code owning team gets an email, which is expected. However, once one member of the team has completed their review of the Pull Request, the team is removed as a reviewer and the individual is added.

This is very undesirable, as now the rest of the code owning team loses visibility of the Pull Request through

Is there any way to change this behaviour?



Hi @dgard1981,

Thank you for being here. Is the  Require review from Code Owners  setting is enabled for the repo in question? The individual approvals won’t satisfy the requirement for code owner approval in a protected branch. Here is a link to our documentation on this setting:

1 Like

Hi @andreagriffiths11,

Thanks for your reply, however I think you may have misunderstood the issue.

Yes, we require review from code owners. To that end we have create a CODEOWNERS file which specifies a single team. This team has been given explicit write permissions to the repository, as described in the documentation, meaning that upon creation of a Pull Request the specified team is added as a reviewer.

So far, so good.

However, when one member of the specified team approves the Pull Request, that member replaces the team as the reviewer for the Pull Request. This means that every other member of the team loses visibility of the Pull Request and won’t be notified about further interactions.

In this case we require two reviews for a Pull Request, so this means that as well as the code owener team we have to manually specify members of that team as individual reviewers. This is both time consuming and inconvinient.

I hope that better explains my issue.




+1 For this issue.
andreagriffiths11 are you aware of a setting that can stop the behavior dgard1981 is describing?

1 Like

@andreagriffiths11 - To confirm, this is still an issue.

GitHub has no concept of ‘default’ reviewers, and the ‘suggestions’ for reviewers when creating a PR are entirely inadequate. So unless we manually add every reviewer individually to every PR, all but one user loses visibility of the PR after an approval - it’s an awful user experience.

1 Like

@andreagriffiths11 This is a major issue for me as well

Joining in to say it would be nice if this could be toggled

Ran into this issue as well…was wondering if I created a second team with all the same people if I could at least get 2 people to be able to review and approve. I have a requirement that I need 2 reviewers and so having the team removed means that I can’t satisfy that requirement

@irwindouglas - We considered that, but then both teams would need to be added as code owners and granted explicit write access to the repository, and we’d have to maintain members in two teams. An ugly solution to be sure.

It appears to be worse than reported above. I’m seeing the behaviour described, but it’s the same if a member of the team simply comments and doesn’t approve/request changes. Aside from the initial email, there’s basically no visibility to team members that there’s a PR to act upon.

Our use-case is that we’d like all members of the team to be made aware of the PR, even if it’s approved/changes requested, until such time as it’s merged - but require only 1 approval minimum


I was expecting when I add a team that it’s effectively the same as adding each member individually… currently when one person approves it removes the rest of the team (not visible in the review request tab to them).

1 Like

+1 on this issue, would love to have the option that leaves the list of reviewers untouched.

1 Like

Thank you for the additional feedback, I’ll be sure to share it with team.
Codeowners and code review assignment are two features that should work with one another as intended. For example:

A pull request that modifies code owned by teamA in a CODEOWNERS file should trigger the team member replacement configured in an enabled code review assignment for teamA .

So far this :point_up: sounds like what is happening in your case,

“meaning that upon creation of a Pull Request the specified team is added as a reviewer”

With that in mind I see the gap to fill use case here, thanks again for taking the time to share.


+1 that I’d like a better way to track all the PRs my team is/was supposed to review. The requested-reviewer and requested-team dropping out once a review happens makes this impossible to track. I put a different but related question here re: managing a team of code reviewers.

Any follow up on this? Our team relies on actively being assigned PRs so when one person approves the next person won’t see the PR in their inbox.

Any news here? We also have the same problem.
We need to keep all the team aligned with ongoing PRs.

Hello, is there any update on this issue? We really like to use teams in CODEOWNERS but with this behavior it’s quite unuseful (when you require more than one approval)

+1 would like to see this problem addressed soon! Our team is growing and we’d like not to have to tag every person on a PR, but need two reviewers!

Please add some UI like most other SCMs have, even if this just writes a CODEOWNERS file. Lead engineers do not have the time to sit there writing CODEOWNERS files across dozens of repos.

+1, this isn’t a blocker for our team, but it is a nuisance and causes a lack of visibility on currently open PR’s.