New command to add Rector to your CI in seconds
We're working hard to make the developer experience as smooth as possible. The fewer steps to your first run and full automation with Rector, the better.
In February, we added improvement for the first run. Now we add a new command to set up Rector in your CI to work for you.
When you run Rector for the very first time, it generates the rector.php config for you. It suggests directories and the first rule to kick off. Let's take this further.
Little preview of what we'll talk about today
- Does your PHPStan fail?
- No worries, just let Rector fix it:
- And soon, your CI is passing and ready for merge ✅
Rector working for you
You often ask, "how can I add Rector to CI to work for me?" In the end, the answer is a short Github Workflow file, but there are few traps on the way:
- it must run only for core developers, who have access to the repository = that way Rector can actually contribute
- it must not run on forks
- it must run only on pull-requests
- the Rector commit must re-trigger the CI Workflows so you have its work verified
- it needs access to the Github token to have enough rights to contribute
This road is pretty cumbersome, right?
Introducing the setup-ci command
Now we turned it to single command that:
- generates
.github/workflows/rector.yaml - fills your repository name to run workflow only for core contributors
- shows you 2 links: to create a Github token and add the token as a repository secret
How to use it?
First, make sure you have the latest Rector 0.15.21, and then run locally:
vendor/bin/rector setup-ci
Follow instructions
-
- generate the token
-
- fill it in the right place
Push a pull-request, make a mistake and see how Rector handles boring work for you.
Happy coding!
