@TomasVotruba let's merge to have faster feedback to test ;)

@gharlan please first clear cache, then run normally after that:

# first required for this change, scans 747 files, change 16 files
vendor/bin/rector --kaizen 1 --clear-cache

# scans 747 files again because there was a 16 files changed on previous run, so probablay there is other next rule to apply
vendor/bin/rector --kaizen 1

Thanks!

The second run is indeed scanning all 747 files again, but it does not apply any rule, so no changes.
(When doing a third run with --clear-cache, the next rule is applied)

I see, it may rely on cache invalidation, so force clear cache is needed before returned when there is file change + kaizen, I will check...

I created new PR for that:

• [Kaizen] Enforce clear cache when there is files changed + kaizen enabled #7052

This pull request has been automatically locked because it has been closed for 150 days. Please open a new PR if you want to continue the work.