Team Foundation Server Check-In Policies

Visual Studio Team System (VSTS) Blog - Available Check-In-Policies for Team Foundation Server

This post lists a number of different check-in policies for TFS. Those that come with TFS, from the VS SDK, built by the community and those coming from Microsoft in the Check-in Policies Pack

One of the community written ones I found interesting was the TFS Code Review Workflow.

"TFS Code Review Workflow: This project is a combination of a Code Review Work Item and a Code Review Check-in Policy. The check-in policy doesn’t allow a check-in unless it has an associated Code Review work item, and that work item is set to approved. Only people in a TFS group named {Project}\Code Reviewers can set an item to approved: Code Review Work Item, Code Review Custom Check-In Policy and Code Reviewers Security Group."

The Check-in Policies Pack also looks interesting;

"Our current plan is to include:

Check-in policy granularity: there is one already in Code Gallery and what we will do is package this, change some of the UI and take out some of the complexity

Work-Item Associations: This is a very cool one that I hope many of you will find useful. You get to specify a query and if the associated work items by the developer are not part of the query results the check-in is blocked. This is very useful when it comes to making sure that check-ins are always associated with approved bugs.

Banned files: this policy allows you to specify a file extension or a regular expression in order to keep files that you don’t want out of version control. This is usually used for dll’s, build artifacts, or some website files that are automatically generated.

Check-in Comments: this policy gets shipped as part of the SDK. It looks at the check-in comments and makes sure it is not blank."

The Check-In Policies pack will also include the source code... ;)

Related Past Post XRef:
"Visual Studio Custom Checkin Policy Template"
TFS Check In Policies, Code to Police Code