Discuss auto-close stale PR's

  1. There are contributors that never apply the requested changes.

What I also have noticed observing the PR’s over the past few weeks is that PR’s made by Core Devs have much shorter cycles in general. Core Devs are faster in reviewing and approving each other’s PR’s. This was shown graphically in the previous discussion: Decision needed: should we close stale PRs? and how many lapsed days are PRs considered stale? - #9 by ammaraskar
This can be explained by the fact that Core Devs are better accustomed to writing code in an acceptable way, but personally I get the feeling that “outsider”-PR’s just get less priority. I can’t back that up with numbers.

So, where does that leave us? These numbers make me reconsider if auto-closing is helping anything… It just masks the problem of not having enough reviewers.

3 Likes