at path：
ROOT
/
wp-content
/
plugins
/
mailchimp-for-wp
/
AGENTS.md
run：
R
W
Run
assets
DIR
2026-03-27 02:20:25
R
W
Run
config
DIR
2026-03-27 02:20:25
R
W
Run
includes
DIR
2026-03-27 02:20:25
R
W
Run
integrations
DIR
2026-03-27 02:20:25
R
W
Run
languages
DIR
2026-03-27 02:20:25
R
W
Run
AGENTS.md
1011 By
2026-03-27 02:20:25
R
W
Run
Delete
Rename
CHANGELOG.md
58.37 KB
2026-03-27 02:20:25
R
W
Run
Delete
Rename
LICENSE
34 KB
2026-03-27 02:20:25
R
W
Run
Delete
Rename
README.md
2.31 KB
2026-03-27 02:20:25
R
W
Run
Delete
Rename
SECURITY.md
495 By
2026-03-27 02:20:25
R
W
Run
Delete
Rename
autoload.php
5.82 KB
2026-03-27 02:20:25
R
W
Run
Delete
Rename
mailchimp-for-wp.php
3.48 KB
2026-03-27 02:20:25
R
W
Run
Delete
Rename
readme.txt
40.17 KB
2026-03-27 02:20:25
R
W
Run
Delete
Rename
uninstall.php
547 By
2026-03-27 02:20:25
R
W
Run
Delete
Rename
wpml-config.xml
1.42 KB
2026-03-27 02:20:25
R
W
Run
Delete
Rename
error_log
up
📄
AGENTS.md
Save
# AGENTS.MD Be concise when opening a pull request. No need for unnecessarily verbose text or endless checklists. The maintainers are mostly interested in special points of consideration when reviewing the code and whether the change introduces any breaking changes. That your code adheres to our coding standards, does not break any tests, uses proper sanitization and escaping, etc. is implied. There is no need to repeat that in text as it makes it easier to miss the important points of your pull request. ## Testing instructions - Find the CI plan in the `.github/workflows` directory. Ensure that your code changes do not break any of the tests in the CI plan. - Run `composer run-script test` to run the PHP test suite. - Run `composer run-script check-syntax` to check for PHP syntax errors. - Run `composer run-script check-codestyle` to check the PHP code style. - Run `composer run-script static-analysis` to run static analysis on the PHP code. - Run `npm run lint` to check the JS code style.