Companion to GitLab issue #3372028.
When users run rector init, Rector generates a bare base rector.php that doesn't register the Drupal deprecation sets. New users then run rector and see no changes (cf. the recurring 'rector runs but produces no diff' reports). We should hook into / document an init path that produces a Drupal-ready rector.php (registering the Drupal sets), so the tool works out of the box.
Companion to GitLab issue #3372028.
When users run
rector init, Rector generates a bare baserector.phpthat doesn't register the Drupal deprecation sets. New users then run rector and see no changes (cf. the recurring 'rector runs but produces no diff' reports). We should hook into / document an init path that produces a Drupal-readyrector.php(registering the Drupal sets), so the tool works out of the box.