When working on a codebase with a team, you always want to make sure, that everything is kept clean and works smoothly. You have git-flow, you have code reviews - they ensure, that everyone can work without impacting others and the main branch is secured. There's one issue however - by default you cannot force team members to go through the whole process - creating a feature branch, pull request, code review. Fortunately VSTS allows you to set a branch policy, which will ensure, that no one breaks the rules.
Setting a branch policy
TO set-up a branch policy just go to Code->Branches page. Choose whichever branch you want and select Branch policies item.
You'll see a page, where you can choose to protect this particular branch. When you select the checkbox, you'll see different options to make sure it is secured. We'll go through each one to get a basic understanding what it gives us.
Minimum number of reviewers
It allows us to define what is the minimum number of reviewers to actually complete a pull request. What is important here is Allow users to approve their own changes checkbox - if you want to force, that someone has reviewed a PR, make sure it is not checked!
Check for linked items
Useful when working with VSTS issue tracker. Allows you to block a PR if a work item hasn't been linked to it.
Check for comment resolution
My favorite. Forces an author of a PR to make sure, that each comment has been reviewed and accepted.
Allows you to link a build definition to queue a build for a PR to make sure, that feature branch passes through the whole pipeline. No more broken builds!
When a branch policy is set, let's try to do following thing - push a commit directly to a develop branch(or any other branch which is protected) and complete a pull request.
Pushing a commit directly to the protected branch will result in an error
In this case both build and approvals weren't finished
As you can see in VSTS you can easily set a branch policies, which will help you secure your main branch from broken features. What is more, they will ensure you, that each team member follows the same process and no change can affect other team members.