Review Assistant tool includes the custom check-in policy for TFS. Check-in policies enforce constraints every time when files are checked into source control.
You can set Visual Studio check-in policies through Team Explorer as documented in this article, the tf.exe configure command, or through registry keys declared in the pkgdef of a Visual Studio extension.
My suggestion is to have your development branch, checkin your code and have it reviewed. Then either make the necessary changes or roll your changes back. This is also good for tracking everything done - your work, the reviewers work, and then, if needed, your revisions from the reviewer comments.
You'll learn how to import your TFS projects and users into Review Assistant, set up roles, and implement pre-commit code reviews using the shelving feature. We will also discuss how to...
Make sure to click the check box next to each file you want to checkin so that it contains a check mark. If you want to keep the files checked out of source control, select Keep Checked Out.
In TFS (VS 2013) the pending changes allows you to see either changes just within the solution i.e. files that are included in a project or all changes that happen in the file system under the solution so you can see all changes and then check them in with one check-in.
This article explains implementation of the TFS custom check-in policy for pre-commit code review. We developed this policy for Review Assistant – our code review tool.
I'm trying to get a list of all check-ins (limited / ordered by date) via the TFS query editor in Visual Studio Team Explorer. I can make a query that lists all bugs, sprint backlog item or product backlog item, but I can't find the actual check-in.
In this video we will learn following: 1. How to Check in and Check out code in TFS 2015? 2. What is local repository in TFS 2015?...more