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
to catch either installed themes and stuff in folders outside of WordPress itself -- as a way to run preflight checks, and potentially tie into deployments and github actions -- would be useful, so themes could be scanned not only from being installed, but arbitrary theme directories that aren't exposed to a functional installation.
The text was updated successfully, but these errors were encountered:
As an ancillary thing, if it would be possible to also have documentation for how to set it up for GitHub actions, I suspect a number of themes that manage their code primarily on gh would be able to leverage it -- not necessarily on every commit, but as a pre-tagging-of-a-release check.
But that would be much more of a subsequent thing down the road.
Previously: #2
Discussed in Slack here:
https://wordpress.slack.com/archives/C02RP4Y3K/p1670944400058739
It feels like being able to run the theme-check via wp-cli as something like
to catch either installed themes and stuff in folders outside of WordPress itself -- as a way to run preflight checks, and potentially tie into deployments and github actions -- would be useful, so themes could be scanned not only from being installed, but arbitrary theme directories that aren't exposed to a functional installation.
The text was updated successfully, but these errors were encountered: