If a Subversion command cannot complete successfully, perhaps due to server problems, your working copy can be left in an inconsistent state. In that case you need to use→ on the folder. It is a good idea to do this at the top level of the working copy.
In the cleanup dialog, there are also other useful options to get the working copy into a
As stated above, this option tries to get an inconsistent working copy into a workable and usable state. This doesn't affect any data you have but only the internal states of the working copy database. This is the actual
Cleanup command you know from older TortoiseSVN clients or other SVN clients.
If checked, all write locks are removed from the working copy database. For most situations, this is required for the cleanup to work!
Only uncheck this option if the working copy is used by other users/clients at the time. But if the cleanup then fails, you have to check this option for the cleanup to succeed.
Changes all file times to the time of the last commit.
Removes unused pristine copies and compresses all remaining pristine copies of working copy files.
Sometimes the shell overlays, especially on the tree view on the left side of the explorer don't show the current status, or the status cache failed to recognize changes. In this situation, you can use this command to force a refresh.
If this is checked, then all actions are done for all files and folders included with the
svn:externals property as well.
This is a fast and easy way to remove all generated files in your working copy. All files and folders that are not versioned are moved to the trash bin.
Note: you can also do the same from the→ dialog. There you also get a list of all the unversioned files and folders to select for removal.
Este comando revierte todas las modificaciones locales que no se han confirmado todavía.
Note: it's better to use the→ command instead, because there you can first see and select the files which you want to revert.