Good issues for new and existing contributors

Want to submit your first pull request to WP-CLIWP-CLI WP-CLI is the Command Line Interface for WordPress, used to do administrative and development tasks in a programmatic way. The project page is http://wp-cli.org/ https://make.wordpress.org/cli/? We’ve identified a few good first issues for you to get your feet wet:

If you’ve contributed to WP-CLI before, here are some reasonably well-defined issues we’d like to see pull requests for:

  • Permit defining ABSPATH before WP-CLI is loaded
    It should be possible to define ABSPATH before WP-CLI is loaded. This issue involves a simple conditional check, and some Behat tests to confirm expected behavior.
  • Move intra-doc links to someplace more prominent
    The top of the command documentation page is less than ideal. If you can provide better HTMLHTML HTML is an acronym for Hyper Text Markup Language. It is a markup language that is used in the development of web pages and websites., I can incorporate it into the developer theme and commit to WordPress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/.
  • Way to distinguish between a user’s direct capabilities and those inherited from their role
    wp user list-roles <user> returns both the capabilities that a user has been directly assigned, and the capabilities that they inherit from their role. For this issue, let’s add a new argument where the user can filterFilter Filters are one of the two types of Hooks https://codex.wordpress.org/Plugin_API/Hooks. They provide a way for functions to modify data of other functions. They are the counterpart to Actions. Unlike Actions, filters are meant to work in an isolated manner, and should never have side effects such as affecting global variables and output. to the origin of the capabilities.
  • wp user remove-cap incorrectly returns success status when attempting to remove cap inherited from a role
    It should instead produce an error stating that the capability is inherited from the role. This issue will involve adding the correct logic with a corresponding functional test.

Read through the contributing guide for details on how to get started. Feel free to ask questions on the specific issue, or join us in the #cli channel with any questions you might have.