Downsides of checking in files that have no changes?

  Uncategorised

Regardless of whether it is a bug, that TFS forces files to be in the pending changes section, even when there are no changes, is there a downside to checking those files in?

Please note that according to this, the way to get rid of files that have no changes, would be to issue the following command with TFS power tools:

tfpt uu /noget /r 

What is the downside of checking in files that have no changes? Does it pose some sort of obstacle to the regular agile TFS workflow? Why shouldn’t I check in files that have no changes?

Source: Visual Studio Questions

LEAVE A COMMENT