Code reviews for your Azure DevOps Server projects will be posted as a "PullRequest" member of your Azure DevOps team. In order to post code reviews, the user must be created in your Azure DevOps.
The Azure DevOps posting user must be created by an individual on your team with the following administrative permissions:
A PullRequest account with an Owner role for the organization in question.
An Administrator role on your Azure DevOps Server Group.
Creating & Adding the Azure DevOps User
Log into the PullRequest Proxy and click the Configure Azure DevOps button on the home page.
Select "Configure Azure DevOps"
Add Root URL
Paste the root URL of your Azure DevOps Server instance (this will be whatever domain your team usually uses to access GitHub). Example:
Create Posting User
Log in to your Azure DevOps instance as an Administrator and create a new user with the username PullRequest. PullRequest reviewers and systems will use this user to post code review content.
We also recommend adding the PullRequest logo as the posting user's avatar:
Download PullRequest Logo Avatar
Add Posting User to Projects
Add the PullRequest user to all of the organizations/repositories you want code review on. Be sure to grant the user the appropriate access so it's able to read repositories and pullrequests, view code and post comments.
Create Azure DevOps Access Token
Log into Azure DevOps as the PullRequest user you just created.
This may be easier in another browser or in an incognito tab so you can remain logged in as the Azure DevOps Administrator user.
Click the profile icon at the top right and click Security from the drop-down menu. From here, click on Personal access tokens from the sidebar on the left. This should be accessible from the following path:
Click New Token and create a Personal Access Token with the following properties:
Code - Read & Write and Status
In order to function properly write permissions are required. PullRequest will never write or modify code in your repositories. Read more about how we keep your code and data secure here.
Once generated, copy the personal access token to your clipboard and go back to the PullRequest Proxy UI with the Azure DevOps Settings modal open.
Add Posting User to Proxy
Enter PullRequest as the PullRequest Username (or whatever name was used in Azure DevOps).
Make sure the PullRequest Username is spelled exactly as the username of the PullRequest user that was created. We highly recommend "PullRequest" (all one word, PascalCase) to maintain communication consistency.
Add Personal Access Token to Proxy
Paste the Personal Access Token into the modal and click Update.
Open the Repositories tab in the left sidebar. The repositories the PullRequest GitHub user were added to should appear in a list here.