Add --network flag for cron event run ✅

Summary

This PR successfully implements the --network flag for the wp cron event run command, allowing users to run cron events across all sites in a WordPress multisite installation with a single command.

Problem Solved

In multisite environments, users previously needed to either:

• Create multiple cron entries (one per site) in crontab
• Use complex bash scripts: wp site list --field=url | xargs -i -n1 wp cron event run --due-now --url="{}"

Now they can simply run: wp cron event run --due-now --network

Implementation Checklist

• Add --network flag to the run() method in src/Cron_Event_Command.php
• Implement logic to iterate through all sites in multisite when --network is used
• Add validation to ensure --network is only used in multisite environments
• Add comprehensive Behat tests for the --network flag functionality
• Address all code review feedback (6 rounds of improvements)
• Refactor to eliminate code duplication with helper method
• Fix test to avoid running WordPress core events
• Run code quality checks (lint, phpcs, phpstan) - all passed ✅
• Run CodeQL security check - no vulnerabilities found ✅

Key Features Implemented

1. ✅ Validates multisite environment using is_multisite()
2. ✅ Retrieves all sites using get_sites() with optimal parameters
3. ✅ Switches to each site using switch_to_blog() and executes cron events
4. ✅ Restores blog context using restore_current_blog() after each site
5. ✅ Works seamlessly with existing flags: --due-now, --all, --exclude
6. ✅ Provides clear error messages for non-multisite installations
7. ✅ Shows total events executed across all sites with proper pluralization
8. ✅ Counts all sites processed (not just sites with events)
9. ✅ Cleans up 'network' flag before passing to helper methods
10. ✅ Logs debug messages when sites have no events (with --debug=cron)
11. ✅ Extracted event execution logic to reusable helper method (DRY principle)

Code Quality - All Checks Passed

• ✅ Linter - No syntax errors
• ✅ PHPCS - Code style compliant with WP_CLI_CS standard
• ✅ PHPStan - No static analysis errors
• ✅ CodeQL - No security vulnerabilities detected
• ✅ Code Review - All feedback addressed (6 rounds)

Tests Added

Two comprehensive Behat test scenarios in features/cron-event.feature:

1. Non-multisite test - Validates proper error handling
2. Multisite test - Validates successful execution across multiple sites (fixed to run specific events)

Example Usage

# Run all cron events due right now across all sites in a multisite
$ wp cron event run --due-now --network
Executed the cron event 'cron_test_1' in 0.01s.
Executed the cron event 'cron_test_2' in 0.006s.
Success: Executed a total of 2 cron events across 3 sites.

Files Changed

• src/Cron_Event_Command.php (+29 lines, -26 lines) - Main implementation with helper method
• features/cron-event.feature (+39 lines) - Test coverage

Code Review Improvements Made

1. Fixed site_count to count all sites (not just sites with events)
2. Used Utils\pluralize() consistently for both 'cron event' and 'site'
3. Simplified success message format
4. Improved test assertion to validate complete message format
5. Removed 'network' flag from args before passing to get_selected_cron_events
6. Added debug logging when sites have no events to run
7. Refactored duplicate event execution code into private helper method
8. Removed unused $result variable assignments
9. Fixed test to run specific events instead of all due-now events

Ready for Review ✅

All implementation tasks completed, all code quality checks passed, all code review feedback has been addressed, and test failure fixed. The feature is ready for final review and merge.

• Fixes Add --network flag for event run #117

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.