本文档针对 WordPress 开发者,提供了当 Pull Request 未获评审时的实用策略,核心在于通过简化评审过程、提供清晰上下文和主动参与社区来吸引关注。
Sometimes we publish a Pull Request and no one reviews our work. What to do?
Attracting a review largely isn’t about the code – it is about making the reviewing easy.
If you published a Pull Request that isn’t getting any comments or reviews, try one of the strategies used by core contributors:
Approving a 2000-line-long PR takes months and feels overwhelming.
Approving a 50-line long PR takes days or hours and feels easy.
Large batches slow you down. Ship your work in small chunks to merge more and learn faster.
Clarify:
* What problem are you solving?
* How does your PR solve it?
* What feedback do you need?
* What’s out of scope?
* What’s unintuitive?
* How to test?
Summarize any related issues and PRs.
It’s easier than asking others to go and figure it out.
All contributions are competing for attention. Make your stand out.
The easiest way? Say why it matters:
❌ A new react hook to get data
✅ useEntityRecord: get data with 10x less boilerplate
Then prove it with code examples, visuals, and screencasts.
Post a link to your PR in related issues & PRs.
Ping commenters of related issues, previous committers, and tech leads.
Bring it up on the #core-editor channel of the WordPress.org slack. The easiest way to get feedback is to speak out during the open floor section of the weekly Core Editor meeting.
Assign relevant labels, milestones, and projects (or ask someone).
It’s the easiest way to get on others’ radar.
Look up the PRs of commenters of related issues, previous committers, and tech leads. Then review them.
Is their work unfamiliar? Do:
Risk adds friction – an approval can backfire later.
Clarity is like grease. Clearly document:
Some PRs naturally get more traction than others.
Double down on these.
Some Issues are more topical than others (e.g. those listed in the goals for an upcoming release) and thus will garner more attention. By focusing on these it will be easier to attract reviewers.
How to get there quickly? Help with an active project from the WordPress roadmap