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.
- 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.
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:
- Take some time to understand it
- Propose a pair programming session
- Skip, go for the next PR
Risk adds friction – an approval can backfire later.
Clarity is like grease. Clearly document:
- What risks are involved? Why take them?
- Why is this PR the best solution?
- How can the risk be minimized?
- What else has been tried?
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