alt Hacker NewsLocking down pr is the wrong approach (for most). Just provide a subtab inside PR tab that shows PRs from new people. One tab for pr from contributors and users who already have PRs accepted in the repo.
Another tab from first time/no pr approved yet users. Maintainers can treat it as spam box if they want.
Occasionally, users can flag them as useful and maintainers can then look at them.
Give a button to move from others to PR tab.
Don't consider count of PRs inside others in the main count.
Replies
> Locking down pr is the wrong approach (for most).
Depends on your goal no? If your goal is to not accept random contributions or PRs, then being able to disable PRs completely, seems like the perfect approach? Up until this change (which happened almost a year ago, FWIW), it was impossible to just have a read-only mirror on GitHub that didn't get hit with drive-by PRs that just waste time, for example: https://github.com/videolan/dav1d/pulls?q=is%3Apr+state%3Acl...
I'm glad we can finally completely disable it, as it seems to just confuse people when you're not actually accepting PRs.
Agreed. So many things could be solved by smart UIs. This is pouring the baby out with the bathwater.