Welcome to WP-CLI Hack Day! We appreciate you taking time to contribute to the project.
We'd love to help you submit at least one pull request today. Given this goal, you'll likely want to start with something small and attainable. After you've submitted your first pull request for the day, you're welcome to work on something more ambitious.
When do you submit a pull request during Hack Day, please add Related wp-cli/wp-cli#5859
so we can easily keep track of them. We'll include them in a recap post at the end of the day.
We put together this guide to make contributing as straightforward as possible. Please also join the #cli channel in WordPress.org Slack (sign up instructions) to chat with other contributors, for questions, etc.
Your leads for the day are: schlessera, danielbachhuber, swissspidy
During the Hack Day, we’ll have two open video chat sessions:
- 🕓 00:00-01:00 PST / 03:00-04:00 EST / 08:00-09:00 UTC / 09:00-10:00 CET / 17:00-18:00 JST
- 🕓 07:00-08:00 PST / 10:00-11:00 EST / 15:00-16:00 UTC / 16:00-17:00 CET / 00:00-01:00 JST
These sessions are a great opportunity to discuss remaining issues live, chat about the progress we’ve made, and to connect with the community. Feel free to join these to talk through any challenges or share your updates!
If you normally use WP-CLI on your web host or via Brew, you're most likely using the Phar executable (wp-cli.phar
). This Phar executable file is the "built", singular version of WP-CLI. It is compiled from a couple dozen repositories in the WP-CLI GitHub organization.
In order to make code changes to WP-CLI, you'll need to set up the wp-cli-dev
development environment on your local machine. Before you can proceed, though, you'll need to make sure you have Composer, PHP, and a functioning MySQL or MariaDB server on your local machine.
Once the prequisites are met, clone the GitHub repository and run the installation process:
git clone https://github.com/wp-cli/wp-cli-dev wp-cli-dev
cd wp-cli-dev
composer install
composer prepare-tests
The wp-cli-dev
installation process clones all of WP-CLI's repositories to your local machine. After the installation process is complete, you can make changes in whichever repository you like. You'll need to fork the repository in order to push your feature branch, however. GitHub's CLI is pretty helpful for this:
cd core-command
gh repo fork
All WP-CLI pull requests are expected to have tests. Watch a ~10 minute video introduction, or see running and writing tests for the written version.
To help you be successful during the day, we curated a list of reasonably approachable and actionable issues.
Feel free to comment directly on the issue if you plan to work on it. We don't usually assign issues, so no need to worry about that.
New contributors
- Admin context crashes because of admin.php file formatting
- Add url-to-id commands for each entity
- Support multiple roles in user add-role and user remove-role
- Support for forcing an update check
- Output only matching IDs in db search
- Provide hardcoded edge case for hello plugin installed by Core
See issues labeled 'good-first-issue' for a broader list.
Seasoned contributors
- Set WP_CLI_PACKAGES_DIR in config file
- Improve speed of import when uploads are available locally
- Introduce a dedicated search-replace url command
- Path errors when running wp dist-archive on Windows
- Prompt if archive file already exists, instead of overwriting automatically
You're obviously welcome to work on any other issue you'd like too! Bug fixes are very welcome. This day can be a good opportunity to discuss trickier issues and brainstorm approaches.
We appreciate your taking the time to participate in the Hack Day and contribute to wp-cli
. Have fun, and we look forward to seeing you on Slack!