-
-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
QA Refresh: Upgrade Psalm, Add PHPStan + composer-require-checker #65
base: 1.16.x
Are you sure you want to change the base?
Conversation
Signed-off-by: George Steel <[email protected]>
Signed-off-by: George Steel <[email protected]>
Signed-off-by: George Steel <[email protected]>
Signed-off-by: George Steel <[email protected]>
Signed-off-by: George Steel <[email protected]>
Signed-off-by: George Steel <[email protected]>
Some issues have been added to the baseline Signed-off-by: George Steel <[email protected]>
Testing out a stricter set of QA tooling to see how we go. Adding PHPStan to existing pipelines will help migration away from Psalm if that becomes necessary - and running both is not a bad idea anyhow! |
Copying the file to every repository does not seem very future-proof to me. 🤷🏻♂️ |
Got any ideas for automating OTOH, It's plausible that Makefiles might diverge in different repos… Do you see it as a problem to use make? I personally much prefer it to composer scripts and things like building docker images etc can't really be done in composer. |
No, of course not but in copy and paste. |
Make itself isn't really reuse-friendly. We could make a reusable nix derivation containing a make entry-point perhaps? That would be supported by renovate. |
OK, now you've lost me 😂 |
@Ocramius |
Roughly, yes: I'm very new to it as well though 😁 |
final
intest
or@final
insrc
psr/container
from dependencies (It doesn't exist)composer-require-checker
to local tools and to CIMakefile
for running QA and building docs locally