My specific use case is this: I have a File System repository which I use to download a set of data files from a server, which I then use in my build. During the build, these data files get modified, used to generate a zip file, and then can be discarded.

When I trigger the next build, however, the checked out files are not overwritten by the Checkout step, because they are the same or newer than those in the repository. I had to write a special Builder step to remove the files before calling the Checkout step.

Please add a flag to the File System repository which forces a clean sync of all files in the repository which are different from (not just newer than) those already checked out. I can also see where this capabilty may be useful for other types of repositories, where checked out data may be modified or deleted. If set, the Checkout action should do whatever is necessary to make the checked out files match those in the repository.