[wp-trac] [WordPress Trac] #57426: Coding Standards: mark warnings that trigger CI failures as errors.
WordPress Trac
noreply at wordpress.org
Fri Jan 6 22:21:19 UTC 2023
#57426: Coding Standards: mark warnings that trigger CI failures as errors.
--------------------------------------------+------------------------------
Reporter: peterwilsoncc | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Build/Test Tools | Version:
Severity: normal | Resolution:
Keywords: has-patch has-unit-tests close | Focuses: coding-
| standards
--------------------------------------------+------------------------------
Comment (by peterwilsoncc):
To be clear, I'm not suggesting changes to WordPress-Core, rather the
wordpress-develop xml config. That's why I am opening a ticket here rather
than on the GitHub repo.
I understand errors and warnings are semantically different, however the
CI treats warnings as errors in the tests directory so I think that needs
to be reflected in the developer workflow. The semantic difference in the
tests directory has been lost.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/57426#comment:7>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list