New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provide a standardized (or even automated) way of working on WP-CLI as a whole #4750

Open
schlessera opened this Issue Mar 27, 2018 · 0 comments

Comments

1 participant
@schlessera
Member

schlessera commented Mar 27, 2018

Development on the WP-CLI "organization" as a whole is currently not well supported, and even less documented/automated.

The best bet so far is to pull in wp-cli/wp-cli and do a composer install --prefer-source. However, this is still far from ideal:

  • Your development is now done in the vendor/wp-cli/* subfolders. Most IDEs hide these by default and/or skip them during indexing.
  • Running the tests inside of one of these pulled-in commands directly means you need to do a composer install within the command folder again ... pulling in the entire bundle with framework and all commands once again. This wastes a lot of space and slows down indexing unnecessarily.
  • When working on multiple commands in this way, using composer install --prefer-source all the time, is a surprisingly quick way of hitting the Github rate limiter.
  • Changes that need to be done for multiple commands need to be done manually for each command and then commit/PRed separately. This can of course be shell-scripted, but an automated mechanism would be hugely useful here.

I'd like to start discussing how best to approach the above problems so that there's an efficient and hassle-free way of working across the multiple repositories for all of the usual maintenance/development tasks.

Once #4748 is done, we should probably start with a small CLI tool inside of the wp-cli/wp-cli-phar package that allows bulk-operations like get/change command versions and similar.

@schlessera schlessera added this to the 2.0.0 milestone Mar 27, 2018

@schlessera schlessera modified the milestones: 2.0.0, 2.1.0 Aug 10, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment