Use GitHub actions

[Zodiac1978]

Add some Continuous Integration CI/CD workflow:

• GitHub action for deployment to wordpress.org
• GitHub action for static analysis (e.g. PHPStan)
• GitHub action for searching for typos
• GitHub action for checking for WordPress coding standards (WPCS)
• GitHub actions for Plugin Check

[apermo]

Which exact WPCS ruleset are you aiming for? I'm happy to provide the PR for that. Do you intend any customizations, modernizations or hardening?

[Zodiac1978]

As a first iteration I would just stick with the official one:
https://github.com/wordpress/wordpress-coding-standards

Do you have any recommendations for customizations, modernizations or hardening?

Personally I would ignore Yoda conditions, because I don't see the advantage.

[apermo]

i have made my own https://github.com/apermo/apermo-coding-standards which are basically

WPCS

• Without Yoda
• With short array
• Requiring Type Hints
• Requiring Return Types
• Allowing Short Ternaries
• require over include
• hooks require a PHPDoc
• Length limits for closures
• nesting of closures and fn is forbidden
• complexity limits
• and a few more

Basically I borrowed a lot from YoastCS enriched with Slevomat and had AI write a few custom sniffs.
If you want to adopt them, feel free, you can always import them and customize them via your phpcs.xml(.dist)