We run Prettier on other projects prior to release to check for regressions. (See Release Checklist)
We used to do that manually.
This is a lot of work, so we use GitHub Actions to automate it.
Create an issue comment like the one below:
RUN alternative_version
RUN alternative_version VS original_version
RUN alternative_version ON repositories
RUN alternative_version VS original_version ON repositories
RUN, VS, ON directives are case-insensitive.
Required.
There are 2 ways to specify.
- Versions or repository name + ref (e.g.
2.0.0,1.7.1, orsosukesuzuki/prettier#2f3fc241f8cb1867a0a3073ceac9d662e4b25fab), it's installed directly withyarn add, so anything thatyarn addallows - Pull Request number on prettier/prettier repository (e.g.
#110168).
RUN #110168
RUN sosukesuzuki/prettier#fix-foo
Optional.
Uses prettier/prettier by default, same syntax as original_version
RUN #110168 VS sosukesuzuki/prettier#fix-foo
RUN sosukesuzuki/prettier#fix-foo VS 1.0.0
Optional.
Run all repositories by default.
Comma separated repository or name list. (Currently only allow repositories defined in repositories.json)
RUN #110168 ON babel/babel
RUN #110168 ON babel/babel,prettier/prettier
RUN #110168 VS 1.0.0 ON babel/babel,prettier/prettier
Run yarn add-repository
