The discussion revolves around the process for getting a theme-component PR reviewed, particularly for the easy-responsive-footer plugin. ganncamp submitted a revised PR after cleaning up their initial messy attempt and asked whether there’s a typical review timeline or if they should have requested approval before implementing the feature. awesomerobot clarified that while no formal timeline exists, posting on Meta helps draw attention — and they committed to reviewing the PR within a day or two. nathank shared another pending PR, unsure how to nudge reviewers without seeming pushy. chapoi offered to personally help get it noticed. The PR was eventually merged by awesomerobot. JammyDodger reopened the topic to address the broader question of how to effectively chase PR reviews, especially for core or official plugins. They suggest opening a Development topic on Meta and tagging them directly — they’ll personally follow up to ensure the PR gets reviewed or at least acknowledged. The consensus is that Meta posts and direct tags are the most effective ways to get attention, since many maintainers don’t actively monitor GitHub PRs.
I’ve reopened this one as though this particular PR has been merged the general question of what to do to nudge a PR is still a little open.
From my viewpoint, I don’t keep track of PRs on GitHub () so I think if we’re looking for a more formal answer to ‘what can I do to chase up a PR review for core or something official’ I think opening a Development topic here on meta would be a good way to get it some extra attention. Feel free to @JammyDodger me and I’ll do my best to hound people and get it reviewed (or at least looked at).