Open marincarroll opened 4 months ago
See my similar report on version 17.6.4 (Most requested changes are the same) https://github.com/WordPress/gutenberg/issues/58790
Hi @marincarroll - is there a different resolution required for each of these issues? Or can a single issue cover both of them?
Hi @marincarroll - is there a different resolution required for each of these issues? Or can a single issue cover both of them?
Thanks for your response! There are multiple. You're probably right that they should be broken into different issues.
Hey, @anton-vlasenko
Maybe you could help us out here.
Hmm,
WordPress.Security.EscapeOutput.OutputNotEscaped
WordPress.Security.EscapeOutput.ExceptionNotEscaped
Squiz.PHP.CommentedOutCode.Found
These linter rules seem like the rules from the WordPress-Extra
ruleset, but Gutenberg doesn't use that ruleset.
It's likely that the wpcomvip
organization's repositories use WordPress-Extra
, which is why the bot is complaining.
The specific files that the bot is complaining about need to be checked to confirm whether these complaints are valid/legitimate and related to upgrading to 17.7.0.
Description
In repos belonging to the
wpcomvip
organization, an attempt to update to 17.7.0 results in the VIP Code Analysis Bot requesting numerous changes. (Most errors/warnings are associated withWordPressVIPMinimum
, but some areWordPress
and someSquiz
).Step-by-step reproduction instructions
1) Update Gutenberg to 17.7.0 in a repo belonging to the
wpcomvip
organization. 2) Open a PR for the changed plugin files. 3) Wait for VIP Code Analysis Bot to request changesScreenshots, screen recording, code snippet
Environment info
Environment info is n/a because this is an issue that occurs during the PR process.
Please confirm that you have searched existing issues in the repo.
Yes
Please confirm that you have tested with all plugins deactivated except Gutenberg.
Yes