Improve Built-in Check-in Policies

By Michael Flanakin @ 5:47 PM :: 2279 Views :: Visual Studio, (Open), (Unreported) :: Digg it!

As I mentioned yesterday, I like the idea of check-in policies, but they are pretty annoying for those of us who like to check-in as much as possible. Why? Because you always have to rerun code analysis and tests before checking code in. Most of the time, this isn't a big deal. If I make a minor change like correct spelling in comments, I have to rerun both. Tell me what test is going to change based on a comment. None. Admittedly, some code analysis rules check for that, but is that really going to provide you much of anything? I just want check-in policies to have some sort of logic to identify whether or not there's any value in running them.