scaffold-package-command
scaffold-package-command copied to clipboard
wp-cli
Scaffolds WP-CLI commands with functional tests, full README.md, and more.
Blocked by https://github.com/probot/settings/issues/3 From https://github.com/wp-cli/wp-cli/issues/3857
## Bug Report - [x] Yes, I reviewed the [contribution guidelines](https://make.wordpress.org/cli/handbook/contributing/). - [x] Yes, more specifically, I reviewed the guidelines on [how to write clear bug reports](https://make.wordpress.org/cli/handbook/bug-reports/). **Describe the current,...
When scaffolding a README file through the `wp scaffold package-readme` command, the command namespaces do not produce any meaningful result. Here's an example output: https://github.com/wp-cli/makepot-command/blob/490b759eb0fe0a4c09d350ba7262d0b0a558248a/README.md#wp-i18n
## Bug Report **Describe the current, buggy behavior** when running $ wp scaffold package anauthor/test --dir=~/testscaffold or $ wp scaffold package-tests ~/testscaffold --force I get multiple errors about not not...
As an example, the changes in https://github.com/wp-cli/entity-command/pull/213 are not being added to the `README.md` file when regenerating it.
We should make sure each scaffolded package includes a proper LICENSE file From https://github.com/wp-cli/restful/issues/97
For packages with a lot of (sub)commands, it could be useful to have a concise TOC section (table of contents), cf. e.g. the readme of https://git.io/v5THM
In our default scaffolded `bin/test.sh`, we should have some feature for failing the build when the scaffolded README is out of date. Functionally, we'd test this by running `wp package...
A la https://github.com/wp-cli/wp-cli/pull/3472
In addition to running the test suite against the nightly build, which we already do, it would be helpful to have it run against the latest stable WP-CLI version too....