Auto-sync CI status for each package

[romainmenke]

Which issue, if any, is this issue related to?

Closes #22

Is there anything in the PR that needs further explanation?

See https://github.com/romainmenke/stylelint-ecosystem-tester/tree/main?tab=readme-ov-file#packages

---

I worked on a separate fork so that I could more easily test everything without causing noise here.

Let me know if you want me to also setup a branch here with the changes if that makes it easier to do code review.

---

What I like about this approach:

• the readme is really clear
• the statuses are always up to date

But there are also some things I don't like.

There are ±50 workflows named latest and another ±50 named next

I don't like that the workflows UI on GitHub becomes much harder to navigate when there are so many workflows and when they all have the same name.

---

This is needed to get nice labels :

---

The checks do have nice names :

Apparently GitHub sends a notification for each failing workflow.

Each time there is an issue it would ping the person who last altered the cron schedule. This is pretty random and noisy.

But maybe this is ok?

Our aim is to have this as green as possible.
Each time a package fails either we broke something in a Stylelint update, or the package author broke something. So the notification could be regarded as useful.

(I've already fixed stylelint-use-nesting)

[ybiquitous]

@romainmenke Thank you for the great improvement! Overall, I love this change. 😄

I don't like that the workflows UI on GitHub becomes much harder to navigate when there are so many workflows and when they all have the same name.

I have the same opinion on this. 😅

Instead, I feel that the {package} / {stylelint_version} / test order is better. Any thoughts?

[romainmenke]

Instead, I feel that the {package} / {stylelint_version} / test order is better.

Yes, I think that might be better :)

---

What do you think of using an npm badge instead of the package name?
This would reduce the width and duplication in the table a bit.

vs.

[ybiquitous]

Thanks. I love the npm badge idea!

[ybiquitous]

Thanks a lot! This is a great achievement. Feel free to merge. 😄 👍🏼

[Mouvedia]

Once WordPress/gutenberg#64828 is merged, we will have to change the test command for @wordpress/stylelint-config.
i.e. it's run from here

[mikeybinns]

Once WordPress/gutenberg#64828 is merged, we will have to change the test command for @wordpress/stylelint-config. i.e. it's run from here

The test:unit command would run the unit tests for all packages. To test just the stylelint package, you can do this command:

npm run test:unit -- --testPathPattern packages/stylelint-config