How can I make meaningful validation comments in Team Foundation?

Question

I have a team of developers who have a bad habit, they write bad comments to check, which makes it a nightmare when we need to look at the history of files on the foundation of the team. I have included a comment policy for changes , so they can even leave a comment on their checks (otherwise they will not).

We had some discussions about the quality of work for the team, and they are okay with things to remind them to follow the established rules for the team, for example, to make them comment. The goal here is to get TFS to warn them that they need to write something longer than “Fixed a problem” or “Updated,” and they must be followed if respected. I am responsible for the scope of our application, and I usually write messages to remind them of things similar to how VS warns them of missing comments or broken code

Now I want to avoid the fact that they simply comment on one word or even a point on their controls. I want to force at least 20 characters to be written before they can verify the changes . Is it possible? How can I do that?

We do not work with the assembly server or work items (we use redmine for tickets).

Answer 1

It seems you can write your own policies. You can refer to this page for more information:

http://blog.devart.com/creating-tfs-custom-check-in-policy-part-1.html

And here is an example of accessing comments:

https://msdn.microsoft.com/en-us/library/bb668980.aspx

Answer 2

, , . , , 20 , , , , , checkin checkin checkin checkin "" ................................... "?

.

, , :

• Visual Studio
• ,
• - TFS 2015+.
• Git repos
• Visual Studio/TFS,

:

6. , , .