upskill-event-manager/wordpress-dev/wordpress/wp-content/plugins/astra-pro-sites/phpcs.xml
bengizmo d1509b3d60 feat(dev-env): implement backup-based development workflow
This commit introduces a more reliable and consistent approach to setting up
the development environment using backups:

- Add setup-from-backup.sh script for environment setup from existing backups
- Standardize script naming and organization
- Move obsolete scripts to bin/obsolete directory
- Update documentation with new workflow instructions
- Create migration guide for transitioning to new workflow
- Update Memory Bank with workflow improvements

The new workflow provides:
- More reliable environment setup
- Faster setup process
- Offline development capability
- Consistent development environments across team members

Breaking changes:
- setup-dev.sh is replaced by setup-from-backup.sh
- sync-and-setup.sh is replaced by separate scripts
- verify-with-wpcli.sh is no longer used

Migration path is documented in MIGRATION_GUIDE.md
2025-03-26 11:26:18 -03:00

78 lines
3 KiB
XML

<?xml version="1.0"?>
<ruleset name="WordPress Coding Standards for Plugins">
<description>Generally-applicable sniffs for WordPress plugins</description>
<!--
Prevent errors caused by WordPress Coding Standards not supporting PHP 8.0+.
See https://github.com/WordPress/WordPress-Coding-Standards/issues/2035
-->
<ini name="error_reporting" value="E_ALL &#38; ~E_DEPRECATED" />
<rule ref="PHPCompatibilityWP">
<exclude-pattern>tests/</exclude-pattern>
</rule>
<config name="testVersion" value="5.3-"/>
<rule ref="WordPress-Core" >
<!-- Double arrow alignment requirement adds unwanted changes if you add/remove any parameter from the array -->
<exclude name="WordPress.Arrays.MultipleStatementAlignment.DoubleArrowNotAligned" />
<exclude name="WordPress.PHP.DevelopmentFunctions.error_log_trigger_error" />
<exclude name="Generic.Formatting.MultipleStatementAlignment.NotSameWarning" />
</rule>
<rule ref="WordPress-Docs" >
<exclude-pattern>tests/</exclude-pattern>
</rule>
<rule ref="WordPress-Extra" >
<exclude-pattern>tests/</exclude-pattern>
</rule>
<!--
Restore the ability to have multiple arguments per line
WPCS disallowed this behaviour in 1.1.0
Ref: https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/commit/bb8a48671e213a5588a6439ea52411eeefab4b0f
-->
<rule ref="PEAR.Functions.FunctionCallSignature">
<properties>
<property name="allowMultipleArguments" value="true"/>
</properties>
</rule>
<rule ref="WordPress-VIP-Go">
<exclude name="WordPressVIPMinimum.Functions.RestrictedFunctions.term_exists_term_exists" />
<exclude name="WordPressVIPMinimum.Classes.RestrictedExtendClasses.wp_cli" />
<exclude name="WordPressVIPMinimum.Functions.RestrictedFunctions.wp_remote_get_wp_remote_get" />
<exclude name="WordPressVIPMinimum.Functions.RestrictedFunctions.get_page_by_path_get_page_by_path" />
<exclude name="WordPressVIPMinimum.Functions.RestrictedFunctions.get_page_by_title_get_page_by_title" />
<exclude name="WordPressVIPMinimum.Performance.RemoteRequestTimeout.timeout_timeout" />
</rule>
<rule ref="PEAR.Functions.FunctionCallSignature.ContentAfterOpenBracket">
<severity phpcs-only="true">0</severity>
</rule>
<rule ref="PEAR.Functions.FunctionCallSignature.CloseBracketLine">
<severity phpcs-only="true">0</severity>
</rule>
<!-- Check all PHP files in directory tree by default. -->
<arg name="extensions" value="php"/>
<file>.</file>
<!-- Show sniff codes in all reports -->
<arg value="s"/>
<rule ref="WordPress.Files.FileName.InvalidClassFileName" >
<exclude-pattern>*/tests/*</exclude-pattern>
</rule>
<exclude-pattern>*/wordpress/*</exclude-pattern>
<exclude-pattern>*/tests/*</exclude-pattern>
<exclude-pattern>*/node_modules/*</exclude-pattern>
<exclude-pattern>*/vendor/*</exclude-pattern>
<exclude-pattern>*/dist/*</exclude-pattern>
<exclude-pattern>*/admin/*</exclude-pattern>
<exclude-pattern>*/inc/assets/js/dist/*</exclude-pattern>
<exclude-pattern>*/inc/lib/*</exclude-pattern>
<exclude-pattern>/inc/assets/js/main.asset.php</exclude-pattern>
</ruleset>