Repository navigation
Project Management: Exclude PHPStan config and baseline from CODEOWNERS - #86112
Conversation
🤖 PR meta 🤖🎉 PropsIf you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. Props Bot commandsYou can trigger Props Bot actions by commenting on this PR:
Updated as activity occurs, without notifying anyone named here. Add the |
e652341 to
901eaea
Compare
|
cc for awareness @westonruter following #66598 and related to #86088, in case you or another have interest in code ownership over these |
Thanks. I've opened #86204 to add myself as code owner. |
What?
Follow up to #82538 and #82750. Adds
tools/phpstan/base.neonandtools/phpstan/baseline.neonto theExclusionssection at the end of.github/CODEOWNERS.Why?
This reduces the noise from review requests. Like the lint suppression lists, these files change as a side effect of unrelated work. Each PHPStan fix removes entries from the baseline (e.g. #86090, #86096). Without an exclusion,
/toolssends a review request for each such change.How?
Adds the two paths, without an owner, to the existing
Exclusionssection. Last match wins, so they override/tools.Testing Instructions
tools/phpstan/baseline.neon.Use of AI Tools
Claude Code, to add the entries and draft this description. Reviewed by me.
🤖 Generated with Claude Code