Rector automatization: generate commits with every rule changes about rector HOT 3 CLOSED

You can setup github action, like using stefanzweifel/git-auto-commit-action for that for auto-commit, calling another CLI jobs is not part of rector job.

from rector.

Git CLI seems not a rector scope, instead of doing many rules at one, register withRules() one by one instead for new projects ;)

from rector.

Think in way of doing automatic refactoring :)

It's not just a git - it's just kind of integration with anything else.

withShellCmdBetweenRules between refactoring steps could be very flexible:

for eg could

• send mail,
• could do git commit and git push to testing repos/env,
• create PR for review,
• run external php automatic test,
• run code cleanup tools,
• run code formatters,

If nothing like that is inside then we need to write a bash wrapper script for rector. This got some pros and cons and more cons.

Main thing - rector is doing rule1,rule2 checks or file1,file2 ?

from rector.