Skip to content

Conversation

@ernilambar
Copy link
Member

@ernilambar ernilambar commented Nov 21, 2025

Since we are getting lots of false positives on this prefixing check, we are converting ERROR to WARNING for now. Keeping severity 6 to provide more visibility if not ERROR.

@ernilambar ernilambar force-pushed the change-prefixing-error-type branch 2 times, most recently from 0ead139 to ede4629 Compare November 21, 2025 04:40
@ernilambar ernilambar force-pushed the change-prefixing-error-type branch from ede4629 to 0b32a36 Compare November 21, 2025 04:47
@ernilambar ernilambar marked this pull request as ready for review November 21, 2025 04:56
@github-actions
Copy link

github-actions bot commented Nov 21, 2025

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: ernilambar <[email protected]>
Co-authored-by: frantorres <[email protected]>
Co-authored-by: davidperezgar <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@davidperezgar davidperezgar merged commit 59b3c44 into trunk Nov 21, 2025
28 checks passed
@davidperezgar davidperezgar deleted the change-prefixing-error-type branch November 21, 2025 16:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants