Quickly identify what's slow with WordPress
Find a file
Daniel Bachhuber 717ea43c89 Initial commit
2016-07-25 07:36:55 -07:00
bin Initial commit 2016-07-25 07:36:55 -07:00
features Initial commit 2016-07-25 07:36:55 -07:00
inc Initial commit 2016-07-25 07:36:55 -07:00
utils Initial commit 2016-07-25 07:36:55 -07:00
.editorconfig Initial commit 2016-07-25 07:36:55 -07:00
.gitignore Initial commit 2016-07-25 07:36:55 -07:00
.travis.yml Initial commit 2016-07-25 07:36:55 -07:00
command.php Initial commit 2016-07-25 07:36:55 -07:00
composer.json Initial commit 2016-07-25 07:36:55 -07:00
README.md Initial commit 2016-07-25 07:36:55 -07:00
wp-cli.yml Initial commit 2016-07-25 07:36:55 -07:00

runcommand/profile

Profile the performance of a request to WordPress.

Build Status

Quick links: Using | Installing | Contributing

Using

wp profile 

Installing

Installing this package requires WP-CLI v0.23.0 or greater. Update to the latest stable release with wp cli update.

Once you've done so, you can install this package with wp package install runcommand/profile.

Contributing

We appreciate you taking the initiative to contribute to this project.

Contributing isnt limited to just code. We encourage you to contribute in the way that best fits your abilities, by writing tutorials, giving a demo at your local meetup, helping other users with their support questions, or revising our documentation.

Reporting a bug

Think youve found a bug? Wed love for you to help us get it fixed.

Before you create a new issue, you should search existing issues to see if theres an existing resolution to it, or if its already been fixed in a newer version.

Once youve done a bit of searching and discovered there isnt an open or fixed issue for your bug, please create a new issue with the following:

  1. What you were doing (e.g. "When I run wp post list").
  2. What you saw (e.g. "I see a fatal about a class being undefined.").
  3. What you expected to see (e.g. "I expected to see the list of posts.")

Include as much detail as you can, and clear steps to reproduce if possible.

Creating a pull request

Want to contribute a new feature? Please first open a new issue to discuss whether the feature is a good fit for the project.

Once you've decided to commit the time to seeing your pull request through, please follow our guidelines for creating a pull request to make sure it's a pleasant experience:

  1. Create a feature branch for each contribution.
  2. Submit your pull request early for feedback.
  3. Include functional tests with your changes. Read the WP-CLI documentation for an introduction.
  4. Follow the WordPress Coding Standards.

This README.md is generated dynamically from the project's codebase using wp scaffold package-readme (doc). To suggest changes, please submit a pull request against the corresponding part of the codebase.