From b2a65b135dd520279689ebe716eb36d36d03aa57 Mon Sep 17 00:00:00 2001
From: George Stephanis <daljo628@gmail.com>
Date: Thu, 24 Sep 2026 10:28:04 -0400
Subject: [PATCH] Fix PHPCS CI failure: exclude WP-CLI class from VIP-Go
 base-class rule

The `WordPressVIPMinimum.Classes.RestrictedExtendClasses` rule flags
`Two_Factor_CLI_Command extends WP_CLI_Command`, recommending
`WPCOM_VIP_CLI_Command` instead. That base class only exists on
VIP-managed hosting, so it doesn't apply to a generic wordpress.org
plugin -- WP_CLI_Command is the correct base class here.

This warning is currently failing the "Lint PHP & PHP Compatibility
checks" CI job, since the repo's `composer lint` script runs plain
phpcs with no warning-severity suppression.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
---
 phpcs.xml.dist | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/phpcs.xml.dist b/phpcs.xml.dist
index 987b928c6..800e2bc0f 100644
--- a/phpcs.xml.dist
+++ b/phpcs.xml.dist
@@ -16,6 +16,15 @@
 	<rule ref="WordPress" />
 	<rule ref="WordPress-VIP-Go" />
 
+	<!--
+	The WP-CLI command class correctly extends WP_CLI_Command. The VIP-Go
+	ruleset's suggestion to extend WPCOM_VIP_CLI_Command instead only applies
+	to code running on VIP-managed hosting, which this plugin is not.
+	-->
+	<rule ref="WordPressVIPMinimum.Classes.RestrictedExtendClasses">
+		<exclude-pattern>CLI/*.php</exclude-pattern>
+	</rule>
+
 	<!-- disable nonce checks on tests -->
 	<rule ref="WordPress.Security.NonceVerification">
 		<exclude-pattern>tests/*.php</exclude-pattern>