{"id":58705,"date":"2020-03-19T12:22:19","date_gmt":"2020-03-19T20:22:19","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/devops\/?p=58705"},"modified":"2020-03-25T11:30:12","modified_gmt":"2020-03-25T19:30:12","slug":"introducing-the-new-pull-request-experience-for-azure-repos","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/devops\/introducing-the-new-pull-request-experience-for-azure-repos\/","title":{"rendered":"Introducing the New Pull Request Experience for Azure Repos"},"content":{"rendered":"

Pull Requests are a vital feature for many Azure Repos<\/a> customers. We are excited to announce that our new pull request web experience is now available in preview! Not only is the new experience mobile-friendly and faster, we have also added several new features to help you review pull requests quicker and improve your overall pull request experience. Customers will see the preview option rollout in the upcoming weeks.<\/p>\n

Please try out the new experience then let us know your feedback! You can try the new experience by turning on ‘New Repos pull request experience’ in preview through user settings<\/a> or via a banner that will show up once the feature rolls out. After trying it, we would love to hear your feedback: New Repos Pull Request Experience Survey<\/a><\/p>\n

\"Image<\/p>\n

Completion readiness summary in rollup view<\/h3>\n

A pull request with a large amount of policies can really clutter the view and make it difficult to determine the status of a pull request. To help get a quick picture of what the status of a pull request is, we have summed up policies in the overview tab. The rollup view will summarize the policies that are passing\/failing and only surface failed checks. If available, the summary will show a snippet of the failure message from the check’s log. Re-queueing a failed policy is a one-step process. You can view all checks in a panel where you can also re-queue all checks and releases with one click, unless multiple actions can be taken on the check.<\/p>\n

\"Image \u00a0 \u00a0 \"Image<\/p>\n

Add required reviewers per pull request<\/h3>\n

Often times, you want to be able to not just have required reviewers for branches set by policy, but also specific people from different teams to review your pull request and be able to wait on them. With the new experience, you can add reviewers to be required and wait on them to auto-complete. You can do this while creating a pull request or within a pull request in the reviewers section. You can also make existing optional reviewers required or can demote required reviewers to optional, unless they are required by policy.<\/p>\n

\"Image \u00a0 \u00a0 \"Image<\/p>\n

\"Image<\/p>\n

Multiple Iteration select<\/h3>\n

Viewing only subsequent updates when there are several updates doesn’t always give you the full picture of changes made to files. When reviewing files in a pull request, you can now view multiple updates at a time by pressing shift and selecting which updates you’d like to see. So if you’ve already reviewed updates 1-3 but still need to review updates 4-7, you don\u2019t have to view all updates or sift through one update at a time.<\/p>\n

\"Image<\/p>\n

Add suggested changes and commit within a pull request<\/h3>\n

It is often tedious when a reviewer comments on your pull request with a minor change like a syntax fix that then requires you to leave the pull request experience, make the change, commit and push it, and update the reviewer. With suggested changes you can reduce the hassle by using the new “suggest an idea” option! You can include the change you are suggesting within your comment and the pull request author can accept the change without ever leaving the pull request experience. When you’re commenting, you will be able to see a preview of the diff. When you are reviewing you can choose to accept the change and make a commit for each change or batch the suggestions you are accepting to make a single commit for all the changes.<\/p>\n

\"Image<\/p>\n

\"Image<\/p>\n

\"Image<\/p>\n

Auto-complete: wait on optional policies<\/h3>\n

Currently, when a pull request is set to auto-complete, it only waits on required policies that are set by admins. In the new auto-complete panel, you can choose to wait on optional policies as well. Once you have set auto-complete you can see all the policies auto-complete is waiting on when you “view all checks”.<\/p>\n

\n\t\t