Running e.g. spotless:check with ratcheting enabled takes almost 20 seconds on one of my projects, even when no files have been modified.

As it runs other projects much quicker, it leads me to believe that the number of files is the issue.

I believe it currently gathers all files matching the include patterns first, and afterwards matches against what has actually been modified. I'd like being able to configure it to do the opposite, i.e. start with the files that have been modified, and filter them based on the include patterns.

Perhaps this would be an issue when a large number of files that do not match the include patterns have been modified.