You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PHPCS/WPCS is wired up, but there is no static analysis and no test harness in either repo. A scaffolded project therefore starts with no way to run a test, which means it never gets one.
Add to both ls-starter-plugin and ls-starter-theme:
PHPStan config at a realistic starting level with the WordPress stubs, so it passes clean on the scaffold and can be tightened per project.
A phpcs.xml.dist ruleset file rather than relying only on CLI flags in a Composer script — more portable and discoverable.
A PHPUnit setup with a wp-env (or equivalent) harness, plus one trivial passing test that proves the harness works.
Composer and npm scripts for each, wired into the existing code-quality workflow as separate jobs.
Keep the scaffold green: the point is a working harness that passes on an empty template, not a strict configuration that a new project must immediately fight.
Acceptance criteria
composer analyse (or equivalent) runs PHPStan clean on both scaffolds.
phpcs.xml.dist present in both repos and used by the existing PHPCS script.
composer test runs the PHPUnit suite against a wp-env install and the example test passes.
Both new checks run in the code-quality workflow on pull requests to develop and are green on the unmodified scaffold.
CI runtime increase is stated in the PR; the harness must not require credentials or network access beyond package installs.
README documents how to run analysis and tests locally.
Activity