Wala shell

Advanced PHP File Manager

Server IP: 127.0.0.1 | PHP Version: 8.3.30 | Domains Hosted: 54

Name	Size	Last Modified
📁 ..	-	2025-05-25 12:40
📄 .actrc # Configuration file for nektos/act. # See https://github.com/nektos/act#configuration -P ubuntu-latest=shivammathur/node:latest	129 B	2025-05-25 12:40
📄 .distignore .DS_Store .git .gitignore .gitlab-ci.yml .editorconfig .travis.yml behat.yml circle.yml phpcs.xml.dist phpunit.xml.dist bin/ features/ utils/ .zip .tar.gz	157 B	2025-05-25 12:40
📄 .editorconfig # This file is for unifying the coding style for different editors and IDEs # editorconfig.org # WordPress Coding Standards # https://make.wordpress.org/core/handbook/coding-standards/ # From https://github.com/WordPress/wordpress-develop/blob/trunk/.editorconfig with a couple of additions. root = true [] charset = utf-8 end_of_line = lf insert_final_newline = true trim_trailing_whitespace = true indent_style = tab [{.yml,.feature,.jshintrc,.json}] indent_style = space indent_size = 2 [.md] trim_trailing_whitespace = false [{.txt,wp-config-sample.php}] end_of_line = crlf	591 B	2025-05-25 12:40
📁 .git	-	2026-01-27 11:04
📁 .github	-	2025-05-25 12:40
📄 .gitignore .DS_Store .phpcs.xml wp-cli.local.yml node_modules/ vendor/ .zip .tar.gz composer.lock phpunit.xml phpcs.xml *.log	117 B	2025-05-25 12:40
📄 AGENTS.md # Instructions This package is part of WP-CLI, the official command line interface for WordPress. For a detailed explanation of the project structure and development workflow, please refer to the main @README.md file. ## Best Practices for Code Contributions When contributing to this package, please adhere to the following guidelines: * Follow Existing Conventions: Before writing any code, analyze the existing codebase in this package to understand the coding style, naming conventions, and architectural patterns. * Focus on the Package's Scope: All changes should be relevant to the functionality of the package. * Write Tests: All new features and bug fixes must be accompanied by acceptance tests using Behat. You can find the existing tests in the `features/` directory. There may be PHPUnit unit tests as well in the `tests/` directory. * Update Documentation: If your changes affect the user-facing functionality, please update the relevant inline code documentation. ### Building and running Before submitting any changes, it is crucial to validate them by running the full suite of static code analysis and tests. To run the full suite of checks, execute the following command: `composer test`. This single command ensures that your changes meet all the quality gates of the project. While you can run the individual steps separately, it is highly recommended to use this single command to ensure a comprehensive validation. ### Useful Composer Commands The project uses Composer to manage dependencies and run scripts. The following commands are available: * `composer install`: Install dependencies. * `composer test`: Run the full test suite, including linting, code style checks, static analysis, and unit/behavior tests. * `composer lint`: Check for syntax errors. * `composer phpcs`: Check for code style violations. * `composer phpcbf`: Automatically fix code style violations. * `composer phpstan`: Run static analysis. * `composer phpunit`: Run unit tests. * `composer behat`: Run behavior-driven tests. ### Coding Style The project follows the `WP_CLI_CS` coding standard, which is enforced by PHP_CodeSniffer. The configuration can be found in `phpcs.xml.dist`. Before submitting any code, please run `composer phpcs` to check for violations and `composer phpcbf` to automatically fix them. ## Documentation The `README.md` file might be generated dynamically from the project's codebase using `wp scaffold package-readme` ([doc](https://github.com/wp-cli/scaffold-package-command#wp-scaffold-package-readme)). In that case, changes need to be made against the corresponding part of the codebase. ### Inline Documentation Only write high-value comments if at all. Avoid talking to the user through comments. ## Testing The project has a comprehensive test suite that includes unit tests, behavior-driven tests, and static analysis. * Unit tests are written with PHPUnit and can be found in the `tests/` directory. The configuration is in `phpunit.xml.dist`. * Behavior-driven tests are written with Behat and can be found in the `features/` directory. The configuration is in `behat.yml`. * Static analysis is performed with PHPStan. All tests are run on GitHub Actions for every pull request. When writing tests, aim to follow existing patterns. Key conventions include: * When adding tests, first examine existing tests to understand and conform to established conventions. * For unit tests, extend the base `WP_CLI\Tests\TestCase` test class. * For Behat tests, only WP-CLI commands installed in `composer.json` can be run. ### Behat Steps WP-CLI makes use of a Behat-based testing framework and provides a set of custom step definitions to write feature tests. > Note: If you are expecting an error output in a test, you need to use `When I try ...` instead of `When I run ...` . #### Given * `Given an empty directory` - Creates an empty directory. * `Given /^an? (empty\|non-existent) ([^\s]+) directory$/` - Creates or deletes a specific directory. * `Given an empty cache` - Clears the WP-CLI cache directory. * `Given /^an? ([^\s]+) (file\|cache file):$/` - Creates a file with the given contents. * `Given /^"([^"]+)" replaced with "([^"]+)" in the ([^\s]+) file$/` - Search and replace a string in a file using regex. * `Given /^that HTTP requests to (.?) will respond with:$/` - Mock HTTP requests to a given URL. `Given WP files` - Download WordPress files without installing. * `Given wp-config.php` - Create a wp-config.php file using `wp config create`. * `Given a database` - Creates an empty database. * `Given a WP install(ation)` - Installs WordPress. * `Given a WP install(ation) in :subdir` - Installs WordPress in a given directory. * `Given a WP install(ation) with Composer` - Installs WordPress with Composer. * `Given a WP install(ation) with Composer and a custom vendor directory :vendor_directory` - Installs WordPress with Composer and a custom vendor directory. * `Given /^a WP multisite (subdirectory\|subdomain)?\s?(install\|installation)$/` - Installs WordPress Multisite. * `Given these installed and active plugins:` - Installs and activates one or more plugins. * `Given a custom wp-content directory` - Configure a custom `wp-content` directory. * `Given download:` - Download multiple files into the given destinations. * `Given /^save (STDOUT\|STDERR) ([\'].+[^\'])?\s?as \{(\w+)\}$/` - Store STDOUT or STDERR contents in a variable. * `Given /^a new Phar with (?:the same version\|version "([^"]+)")$/` - Build a new WP-CLI Phar file with a given version. * `Given /^a downloaded Phar with (?:the same version\|version "([^"]+)")$/` - Download a specific WP-CLI Phar version from GitHub. * `Given /^save the (.+) file ([\'].+[^\'])? as \{(\w+)\}$/` - Stores the contents of the given file in a variable. * `Given a misconfigured WP_CONTENT_DIR constant directory` - Modify wp-config.php to set `WP_CONTENT_DIR` to an empty string. * `Given a dependency on current wp-cli` - Add `wp-cli/wp-cli` as a Composer dependency. * `Given a PHP built-in web server` - Start a PHP built-in web server in the current directory. * `Given a PHP built-in web server to serve :subdir` - Start a PHP built-in web server in the given subdirectory. #### When * ``When /^I launch in the background `([^`]+)`$/`` - Launch a given command in the background. * ``When /^I (run\|try) `([^`]+)`$/`` - Run or try a given command. * ``When /^I (run\|try) `([^`]+)` from '([^\s]+)'$/`` - Run or try a given command in a subdirectory. * `When /^I (run\|try) the previous command again$/` - Run or try the previous command again. #### Then * `Then /^the return code should( not)? be (\d+)$/` - Expect a specific exit code of the previous command. * `Then /^(STDOUT\|STDERR) should( strictly)? (be\|contain\|not contain):$/` - Check the contents of STDOUT or STDERR. * `Then /^(STDOUT\|STDERR) should be a number$/` - Expect STDOUT or STDERR to be a numeric value. * `Then /^(STDOUT\|STDERR) should not be a number$/` - Expect STDOUT or STDERR to not be a numeric value. * `Then /^STDOUT should be a table containing rows:$/` - Expect STDOUT to be a table containing the given rows. * `Then /^STDOUT should end with a table containing rows:$/` - Expect STDOUT to end with a table containing the given rows. * `Then /^STDOUT should be JSON containing:$/` - Expect valid JSON output in STDOUT. * `Then /^STDOUT should be a JSON array containing:$/` - Expect valid JSON array output in STDOUT. * `Then /^STDOUT should be CSV containing:$/` - Expect STDOUT to be CSV containing certain values. * `Then /^STDOUT should be YAML containing:$/` - Expect STDOUT to be YAML containing certain content. * `Then /^(STDOUT\|STDERR) should be empty$/` - Expect STDOUT or STDERR to be empty. * `Then /^(STDOUT\|STDERR) should not be empty$/` - Expect STDOUT or STDERR not to be empty. * `Then /^(STDOUT\|STDERR) should be a version string (<\|<=\|>\|>=\|==\|=\|<>) ([+\w.{}-]+)$/` - Expect STDOUT or STDERR to be a version string comparing to the given version. * `Then /^the (.+) (file\|directory) should( strictly)? (exist\|not exist\|be:\|contain:\|not contain):$/` - Expect a certain file or directory to (not) exist or (not) contain certain contents. * `Then /^the contents of the (.+) file should( not)? match (((\/.\/)\|(#.#))([a-z]+)?)$/` - Match file contents against a regex. `Then /^(STDOUT\|STDERR) should( not)? match (((\/.\/)\|(#.#))([a-z]+)?)$/` - Match STDOUT or STDERR against a regex. `Then /^an email should (be sent\|not be sent)$/` - Expect an email to be sent (or not). * `Then the HTTP status code should be :code` - Expect the HTTP status code for visiting `http://localhost:8080`.	8.48 KB	2026-01-27 11:04
📄 CONTRIBUTING.md Contributing ============ We appreciate you taking the initiative to contribute to this project. Contributing isn’t 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. For a more thorough introduction, [check out WP-CLI's guide to contributing](https://make.wordpress.org/cli/handbook/contributing/). This package follows those policy and guidelines.	538 B	2025-05-25 12:40
📄 LICENSE The MIT License (MIT) Copyright (C) 2011-2018 WP-CLI Development Group (https://github.com/wp-cli/core-command/contributors) Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.	1.12 KB	2025-05-25 12:40
📄 README.md wp-cli/core-command =================== Downloads, installs, updates, and manages a WordPress installation. [![Testing](https://github.com/wp-cli/core-command/actions/workflows/testing.yml/badge.svg)](https://github.com/wp-cli/core-command/actions/workflows/testing.yml) Quick links: [Using](#using) \| [Installing](#installing) \| [Contributing](#contributing) \| [Support](#support) ## Using This package implements the following commands: ### wp core Downloads, installs, updates, and manages a WordPress installation. ~~~ wp core ~~~ EXAMPLES # Download WordPress core $ wp core download --locale=nl_NL Downloading WordPress 4.5.2 (nl_NL)... md5 hash verified: c5366d05b521831dd0b29dfc386e56a5 Success: WordPress downloaded. # Install WordPress $ wp core install --url=example.com --title=Example --admin_user=supervisor --admin_password=strongpassword --admin_email=info@example.com Success: WordPress installed successfully. # Display the WordPress version $ wp core version 4.5.2 ### wp core check-update Checks for WordPress updates via Version Check API. ~~~ wp core check-update [--minor] [--major] [--force-check] [--field=<field>] [--fields=<fields>] [--format=<format>] ~~~ Lists the most recent versions when there are updates available, or success message when up to date. OPTIONS [--minor] Compare only the first two parts of the version number. [--major] Compare only the first part of the version number. [--force-check] Bypass the transient cache and force a fresh update check. [--field=<field>] Prints the value of a single field for each update. [--fields=<fields>] Limit the output to specific object fields. Defaults to version,update_type,package_url. [--format=<format>] Render output in a particular format. --- default: table options: - table - csv - count - json - yaml --- EXAMPLES $ wp core check-update +---------+-------------+-------------------------------------------------------------+ \| version \| update_type \| package_url \| +---------+-------------+-------------------------------------------------------------+ \| 4.5.2 \| major \| https://downloads.wordpress.org/release/wordpress-4.5.2.zip \| +---------+-------------+-------------------------------------------------------------+ ### wp core download Downloads core WordPress files. ~~~ wp core download [<download-url>] [--path=<path>] [--locale=<locale>] [--version=<version>] [--skip-content] [--force] [--insecure] [--extract] ~~~ Downloads and extracts WordPress core files to the specified path. Uses current directory when no path is specified. Downloaded build is verified to have the correct md5 and then cached to the local filesystem. Subsequent uses of command will use the local cache if it still exists. OPTIONS [<download-url>] Download directly from a provided URL instead of fetching the URL from the wordpress.org servers. [--path=<path>] Specify the path in which to install WordPress. Defaults to current directory. [--locale=<locale>] Select which language you want to download. [--version=<version>] Select which version you want to download. Accepts a version number, 'latest' or 'nightly'. [--skip-content] Download WP without the default themes and plugins. [--force] Overwrites existing files, if present. [--insecure] Retry download without certificate validation if TLS handshake fails. Note: This makes the request vulnerable to a MITM attack. [--extract] Whether to extract the downloaded file. Defaults to true. EXAMPLES $ wp core download --locale=nl_NL Downloading WordPress 4.5.2 (nl_NL)... md5 hash verified: c5366d05b521831dd0b29dfc386e56a5 Success: WordPress downloaded. ### wp core install Runs the standard WordPress installation process. ~~~ wp core install --url=<url> --title=<site-title> --admin_user=<username> [--admin_password=<password>] --admin_email=<email> [--locale=<locale>] [--skip-email] ~~~ Creates the WordPress tables in the database using the URL, title, and default admin user details provided. Performs the famous 5 minute install in seconds or less. Note: if you've installed WordPress in a subdirectory, then you'll need to `wp option update siteurl` after `wp core install`. For instance, if WordPress is installed in the `/wp` directory and your domain is example.com, then you'll need to run `wp option update siteurl http://example.com/wp` for your WordPress installation to function properly. Note: When using custom user tables (e.g. `CUSTOM_USER_TABLE`), the admin email and password are ignored if the user_login already exists. If the user_login doesn't exist, a new user will be created. OPTIONS --url=<url> The address of the new site. --title=<site-title> The title of the new site. --admin_user=<username> The name of the admin user. [--admin_password=<password>] The password for the admin user. Defaults to randomly generated string. --admin_email=<email> The email address for the admin user. [--locale=<locale>] The locale/language for the installation (e.g. `de_DE`). Default is `en_US`. [--skip-email] Don't send an email notification to the new admin user. EXAMPLES # Install WordPress in 5 seconds $ wp core install --url=example.com --title=Example --admin_user=supervisor --admin_password=strongpassword --admin_email=info@example.com Success: WordPress installed successfully. # Install WordPress without disclosing admin_password to bash history $ wp core install --url=example.com --title=Example --admin_user=supervisor --admin_email=info@example.com --prompt=admin_password < admin_password.txt ### wp core is-installed Checks if WordPress is installed. ~~~ wp core is-installed [--network] ~~~ Determines whether WordPress is installed by checking if the standard database tables are installed. Doesn't produce output; uses exit codes to communicate whether WordPress is installed. OPTIONS [--network] Check if this is a multisite installation. EXAMPLES # Bash script for checking if WordPress is not installed. if ! wp core is-installed 2>/dev/null; then # WP is not installed. Let's try installing it. wp core install fi # Bash script for checking if WordPress is installed, with fallback. if wp core is-installed 2>/dev/null; then # WP is installed. Let's do some things we should only do in a confirmed WP environment. wp core verify-checksums else # Fallback if WP is not installed. echo 'Hey Friend, you are in the wrong spot. Move in to your WordPress directory and try again.' fi ### wp core multisite-convert Transforms an existing single-site installation into a multisite installation. ~~~ wp core multisite-convert [--title=<network-title>] [--base=<url-path>] [--subdomains] [--skip-config] ~~~ Creates the multisite database tables, and adds the multisite constants to wp-config.php. For those using WordPress with Apache, remember to update the `.htaccess` file with the appropriate multisite rewrite rules. [Review the multisite documentation](https://wordpress.org/support/article/create-a-network/) for more details about how multisite works. OPTIONS [--title=<network-title>] The title of the new network. [--base=<url-path>] Base path after the domain name that each site url will start with. --- default: / --- [--subdomains] If passed, the network will use subdomains, instead of subdirectories. Doesn't work with 'localhost'. [--skip-config] Don't add multisite constants to wp-config.php. EXAMPLES $ wp core multisite-convert Set up multisite database tables. Added multisite constants to wp-config.php. Success: Network installed. Don't forget to set up rewrite rules. ### wp core multisite-install Installs WordPress multisite from scratch. ~~~ wp core multisite-install [--url=<url>] [--base=<url-path>] [--subdomains] --title=<site-title> --admin_user=<username> [--admin_password=<password>] --admin_email=<email> [--skip-email] [--skip-config] ~~~ Creates the WordPress tables in the database using the URL, title, and default admin user details provided. Then, creates the multisite tables in the database and adds multisite constants to the wp-config.php. For those using WordPress with Apache, remember to update the `.htaccess` file with the appropriate multisite rewrite rules. OPTIONS [--url=<url>] The address of the new site. [--base=<url-path>] Base path after the domain name that each site url in the network will start with. --- default: / --- [--subdomains] If passed, the network will use subdomains, instead of subdirectories. Doesn't work with 'localhost'. --title=<site-title> The title of the new site. --admin_user=<username> The name of the admin user. --- default: admin --- [--admin_password=<password>] The password for the admin user. Defaults to randomly generated string. --admin_email=<email> The email address for the admin user. [--skip-email] Don't send an email notification to the new admin user. [--skip-config] Don't add multisite constants to wp-config.php. EXAMPLES $ wp core multisite-install --title="Welcome to the WordPress" \ > --admin_user="admin" --admin_password="password" \ > --admin_email="user@example.com" Single site database tables already present. Set up multisite database tables. Added multisite constants to wp-config.php. Success: Network installed. Don't forget to set up rewrite rules. ### wp core update Updates WordPress to a newer version. ~~~ wp core update [<zip>] [--minor] [--version=<version>] [--force] [--locale=<locale>] [--format=<format>] [--insecure] ~~~ Defaults to updating WordPress to the latest version. If you see "Error: Another update is currently in progress.", you may need to run `wp option delete core_updater.lock` after verifying another update isn't actually running. OPTIONS [<zip>] Path to zip file to use, instead of downloading from wordpress.org. [--minor] Only perform updates for minor releases (e.g. update from WP 4.3 to 4.3.3 instead of 4.4.2). [--version=<version>] Update to a specific version, instead of to the latest version. Alternatively accepts 'nightly'. [--force] Update even when installed WP version is greater than the requested version. [--locale=<locale>] Select which language you want to download. [--format=<format>] Render output in a particular format. --- options: - table - csv - json --- [--insecure] Retry download without certificate validation if TLS handshake fails. Note: This makes the request vulnerable to a MITM attack. EXAMPLES # Update WordPress $ wp core update Updating to version 4.5.2 (en_US)... Downloading update from https://downloads.wordpress.org/release/wordpress-4.5.2-no-content.zip... Unpacking the update... Cleaning up files... No files found that need cleaning up Success: WordPress updated successfully. # Update WordPress using zip file. $ wp core update ../latest.zip Starting update... Unpacking the update... Success: WordPress updated successfully. # Update WordPress to 3.1 forcefully $ wp core update --version=3.1 --force Updating to version 3.1 (en_US)... Downloading update from https://wordpress.org/wordpress-3.1.zip... Unpacking the update... Warning: Checksums not available for WordPress 3.1/en_US. Please cleanup files manually. Success: WordPress updated successfully. ### wp core update-db Runs the WordPress database update procedure. ~~~ wp core update-db [--network] [--dry-run] ~~~ OPTIONS [--network] Update databases for all sites on a network [--dry-run] Compare database versions without performing the update. EXAMPLES # Update the WordPress database. $ wp core update-db Success: WordPress database upgraded successfully from db version 36686 to 35700. # Update databases for all sites on a network. $ wp core update-db --network WordPress database upgraded successfully from db version 35700 to 29630 on example.com/ Success: WordPress database upgraded on 123/123 sites. ### wp core version Displays the WordPress version. ~~~ wp core version [--extra] ~~~ OPTIONS [--extra] Show extended version information. EXAMPLES # Display the WordPress version $ wp core version 4.5.2 # Display WordPress version along with other information $ wp core version --extra WordPress version: 4.5.2 Database revision: 36686 TinyMCE version: 4.310 (4310-20160418) Package language: en_US ## Installing This package is included with WP-CLI itself, no additional installation necessary. To install the latest version of this package over what's included in WP-CLI, run: wp package install git@github.com:wp-cli/core-command.git ## Contributing We appreciate you taking the initiative to contribute to this project. Contributing isn’t 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. For a more thorough introduction, [check out WP-CLI's guide to contributing](https://make.wordpress.org/cli/handbook/contributing/). This package follows those policy and guidelines. ### Reporting a bug Think you’ve found a bug? We’d love for you to help us get it fixed. Before you create a new issue, you should [search existing issues](https://github.com/wp-cli/core-command/issues?q=label%3Abug%20) to see if there’s an existing resolution to it, or if it’s already been fixed in a newer version. Once you’ve done a bit of searching and discovered there isn’t an open or fixed issue for your bug, please [create a new issue](https://github.com/wp-cli/core-command/issues/new). Include as much detail as you can, and clear steps to reproduce if possible. For more guidance, [review our bug report documentation](https://make.wordpress.org/cli/handbook/bug-reports/). ### Creating a pull request Want to contribute a new feature? Please first [open a new issue](https://github.com/wp-cli/core-command/issues/new) 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](https://make.wordpress.org/cli/handbook/pull-requests/) to make sure it's a pleasant experience. See "[Setting up](https://make.wordpress.org/cli/handbook/pull-requests/#setting-up)" for details specific to working on this package locally. ## Support GitHub issues aren't for general support questions, but there are other venues you can try: https://wp-cli.org/#support This README.md is generated dynamically from the project's codebase using `wp scaffold package-readme` ([doc](https://github.com/wp-cli/scaffold-package-command#wp-scaffold-package-readme)). To suggest changes, please submit a pull request against the corresponding part of the codebase.	15.04 KB	2026-01-27 11:04
📄 behat.yml default: suites: default: contexts: - WP_CLI\Tests\Context\FeatureContext paths: - features	126 B	2025-05-25 12:40
📄 composer.json { "name": "wp-cli/core-command", "type": "wp-cli-package", "description": "Downloads, installs, updates, and manages a WordPress installation.", "homepage": "https://github.com/wp-cli/core-command", "license": "MIT", "authors": [ { "name": "Daniel Bachhuber", "email": "daniel@runcommand.io", "homepage": "https://runcommand.io" } ], "require": { "composer/semver": "^1.4 \|\| ^2 \|\| ^3", "wp-cli/wp-cli": "^2.12" }, "require-dev": { "wp-cli/checksum-command": "^1 \|\| ^2", "wp-cli/db-command": "^1.3 \|\| ^2", "wp-cli/entity-command": "^1.3 \|\| ^2", "wp-cli/extension-command": "^1.2 \|\| ^2", "wp-cli/wp-cli-tests": "^5" }, "config": { "process-timeout": 7200, "sort-packages": true, "allow-plugins": { "dealerdirect/phpcodesniffer-composer-installer": true, "johnpbloch/wordpress-core-installer": true, "phpstan/extension-installer": true }, "lock": false }, "extra": { "branch-alias": { "dev-main": "2.x-dev" }, "bundled": true, "commands": [ "core", "core check-update", "core download", "core install", "core is-installed", "core multisite-convert", "core multisite-install", "core update", "core update-db", "core version" ] }, "autoload": { "classmap": [ "src/" ], "files": [ "core-command.php" ] }, "minimum-stability": "dev", "prefer-stable": true, "scripts": { "behat": "run-behat-tests", "behat-rerun": "rerun-behat-tests", "lint": "run-linter-tests", "phpcs": "run-phpcs-tests", "phpstan": "run-phpstan-tests", "phpcbf": "run-phpcbf-cleanup", "phpunit": "run-php-unit-tests", "prepare-tests": "install-package-tests", "test": [ "@lint", "@phpcs", "@phstan", "@phpunit", "@behat" ] }, "support": { "issues": "https://github.com/wp-cli/core-command/issues" } }	2.26 KB	2025-09-06 07:07
📄 core-command.php <?php if ( ! class_exists( 'WP_CLI' ) ) { return; } $wpcli_core_autoloader = __DIR__ . '/vendor/autoload.php'; if ( file_exists( $wpcli_core_autoloader ) ) { require_once $wpcli_core_autoloader; } WP_CLI::add_command( 'core', 'Core_Command' );	249 B	2025-05-25 12:40
📁 features	-	2026-01-27 11:04
📄 phpcs.xml.dist <?xml version="1.0"?> <ruleset name="WP-CLI-core"> <description>Custom ruleset for WP-CLI core-command</description> <!-- ############################################################################# COMMAND LINE ARGUMENTS For help understanding this file: https://github.com/squizlabs/PHP_CodeSniffer/wiki/Annotated-ruleset.xml For help using PHPCS: https://github.com/squizlabs/PHP_CodeSniffer/wiki/Usage ############################################################################# --> <!-- What to scan. --> <file>.</file> <!-- Show progress. --> <arg value="p"/> <!-- Strip the filepaths down to the relevant bit. --> <arg name="basepath" value="./"/> <!-- Check up to 8 files simultaneously. --> <arg name="parallel" value="8"/> <!-- ############################################################################# USE THE WP_CLI_CS RULESET ############################################################################# --> <rule ref="WP_CLI_CS"/> <!-- ############################################################################# PROJECT SPECIFIC CONFIGURATION FOR SNIFFS ############################################################################# --> <!-- For help understanding the `testVersion` configuration setting: https://github.com/PHPCompatibility/PHPCompatibility#sniffing-your-code-for-compatibility-with-specific-php-versions --> <config name="testVersion" value="7.2-"/> <!-- Verify that everything in the global namespace is either namespaced or prefixed. See: https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/wiki/Customizable-sniff-properties#naming-conventions-prefix-everything-in-the-global-namespace --> <rule ref="WordPress.NamingConventions.PrefixAllGlobals"> <properties> <property name="prefixes" type="array"> <element value="WP_CLI\Core"/><!-- Namespaces. --> <element value="wpcli_core"/><!-- Global variables and such. --> </property> </properties> </rule> <!-- Exclude existing classes from the prefix rule as it would break BC to prefix them now. --> <rule ref="WordPress.NamingConventions.PrefixAllGlobals.NonPrefixedClassFound"> <exclude-pattern>*/src/Core_Command\.php$</exclude-pattern> </rule> </ruleset>	2.19 KB	2025-09-06 07:07
📄 phpstan.neon.dist parameters: level: 9 paths: - src - core-command.php scanDirectories: - vendor/wp-cli/wp-cli/php scanFiles: - vendor/php-stubs/wordpress-stubs/wordpress-stubs.php treatPhpDocTypesAsCertain: false ignoreErrors: - identifier: missingType.iterableValue - identifier: missingType.parameter - identifier: missingType.return	359 B	2025-09-06 07:07
📁 src	-	2026-01-27 11:04
📁 templates	-	2025-05-25 12:40
📄 wp-cli.yml require: - core-command.php	30 B	2025-05-25 12:40

Edit File:

Terminal