[benitoalba]

WP_Comment_Query accepts status => 'any', but the argument documentation omits it. Document that 'any' includes every status, including spam and trash, and overrides other supplied statuses. Clarify that 'all' selects approved and pending comments, and correct the database field references to comment_approved.

Trac ticket: https://core.trac.wordpress.org/ticket/58450

Testing

This changes only the argument documentation. Checked the wording against get_comment_ids() and the existing status tests.

On PHP 8.3.36 with PHPUnit 9.6.38:

• The 9 status tests pass with 21 assertions.
• The complete comment query class passes: 162 tests, 482 assertions.
• PHPCS reports no errors and the same 10 SQL warnings as unchanged trunk. None concern the edited documentation.
• git diff --check passes.

php vendor/bin/phpunit --no-logging tests/phpunit/tests/comment/query.php --filter test_status_
php vendor/bin/phpunit --no-logging tests/phpunit/tests/comment/query.php
php vendor/bin/phpcs src/wp-includes/class-wp-comment-query.php
git diff --check

Use of AI Tools

AI assistance: Yes. OpenAI Codex researched the ticket, drafted the documentation change, ran local validation, and wrote this description.

---

This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

Core Committers: Use this line as a base for the props when committing in SVN:

Props benitoalba, dhruvang21.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

---

Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

• @propsbot add <username> to give props to a GitHub user. Requires write access.
• @propsbot remove <username> to leave a user out of the props. Requires write access.
• @propsbot refresh to refresh this list. Adding the props-bot label works too.