remove a required reviewer from Azure Devops

user_68746 0
Viewed 5479

We have a gentleman who is no longer actively working on a project. The problem is he is a required reviewer on our Pull Requests.

I have not been able to find a way to remove him, and we cannot complete our pull requests.

I have spent several hours looking at every option that I can find.

enter image description here

Update 10/10 -- We attempted to use the API and remove this reviewer and do another PR, but with no luck yet. We have even tried having other reviewers approve, but without the other required one it just will not let us complete. I would be happy to move this question as I know it is not code related, but don't know where to....this is not just a 'what tool do you think is best' question --- we are really in a bind here!

second picture

azure-repos azure-devops
3 Answers

Check Automatically include code reviewers section under Branch policies:

Repos >> Branches >> ... (at your branch) >> Branch policies >> Automatically include code reviewers

If you have access to update them, just delete the unneeded reviewers. If you don't have access, take a look at Branch security, or find a person who has access.

I'm not sure if it will work for current Pull Request, maybe you will need to make it again.

user_121795840

remove a required reviewer from Azure Devops

You need ask someone who has the permissions to Edit policies (Project Administrators) to remove that required reviewer from the Automatically include code reviewers:

enter image description here

Note: You need to check the Branch policies of the branch which you want to merge, for example, you merge from Dev to master, you need check the Branch policies of the master branch.

Then, after remove that required reviewer, you could go back to your pull request and click the X button:

enter image description here

Now, that required reviewer is no needed.

enter image description here

Hope this helps.

user_74607770

Check the branch policy of the parent folder, I was having a similar issue but got resolve when disabling the policy for both the folders.

user_49674790
Related