-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[CI] Make sure packages contain all metafiles #40700
8000 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
Conversation
47e3709
to
edd93cf
Compare
I think I'd prefer making this part of an existing CI file. I don't like the multiplication of eg initialization steps. That'd be better for the planet... :) Doable? |
Nice 😀😃 |
About getting the modified packages, maybe it's not worth it? maintaining these is always costly on the long run. |
|
Thank you for the feedback. Instead of having one job per changed component +1 I now do all the checks in a single job. It means a bit more bash and we have to deal with json objects. I do some grouping and I show clear errors what is wrong. |
01597a1
to
a99061e
Compare
I think this job is a good idea. It's a common mistake to forget adding these files when contributing a new bridge package. |
I removed the debug code. This PR is ready to be merged. |
Thank you @Nyholm. |
Thank you for merging |
This PR introduce a new CI job to just do some checks on a package. It first looks at the git diff to figure out what packages have changed. Then for each changed package it verifies:
If the package is new (license file changed), we also make sure that the package is present in composer.json's replace.
I got this idea after seeing PRs like #40696. And we do add one or two package every month.