Get the most out of your PRs with Branch Policies
Sep 28, 2016Matthew Mitrik (MS)

Summary
This post introduces and details the configuration of branch policies for Git pull requests in Azure DevOps. It covers requiring a minimum number of peer reviews, specifying reviewers for particular file paths or types, and automatically building pull requests before they can be merged. It also explains different strategies for handling build updates when the target branch changes and the option for auto-completing pull requests once all policies are satisfied.
More from the Git CI Integration for Azure DevOps trail
- Generate a GitHub Actions workflow with Visual Studio or the dotnet CLI
- Run your CI with Jenkins and CD with Azure DevOps
- Visual Studio Team Services and Team Foundation Server Java Capabilities Presentation and Demonstration Now Available at java.visualstudio.com
- Getting Started with Selenium Testing in a Continuous Integration Pipeline with Visual Studio
- Release Candidate of Visual Studio 2012 Update 3 now available