docs: record wp-cli-pattern-validate extraction and publish - #193
Merged
Conversation
wp-cli-pattern-validate.php is now also distributed standalone as imagewize/wp-cli-pattern-validate, tagged v1.0.0 and installable via 'wp package install imagewize/wp-cli-pattern-validate' — GitHub shorthand resolution means no separate publish step was needed beyond tagging the repo. wp-ops keeps its own copy as the source of truth for the wp-ops/trellis-ops invocation path; the two are independent copies, not a move.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/wp-cli-package-evaluation.mddescribed extractingwp-cli-pattern-validate.phpinto its own package repo as pending work. It's done — this brings the doc in line with reality.Changes
v1.0.0.wp package install imagewize/wp-cli-pattern-validatealready works today via WP-CLI's GitHub-shorthand resolution — no separate registry submission needed. Listing on the WP-CLI package index is optional follow-up, not a blocker.wp-ops/trellis opsinvocation path; the new repo is a second distribution channel, not a move.Files
docs/wp-cli-package-evaluation.md