Pull request access control and new contributor filtering need
Problem
HackerGitHub introduced new repository PR access configuration settings, but existing solutions fail to meet maintainers' needs for fine-grained filtering, new contributor classification, and spam PR screening. Multiple commenters pointed out the lack of functionality to separate first-time contributor PRs from experienced contributor PRs, making it difficult for maintainers to manage spam PRs (e.g., Hacktoberfest) and lacking priority channels to incentivize high-quality contributions. This exposes shortcomings in current PR access control tools in categorization, spam handling, and contribution incentives.
Pain points
- Lack of classification filtering for new contributor PRs
- Spam PRs (e.g., Hacktoberfest) flood in with no effective screening for maintainers
- Lack of priority or monetization channels to incentivize high-quality contributions
Questions to verify
- Do you need more granular PR access control to distinguish first-time and experienced contributors?
- Would you be willing to incentivize high-quality contributions via payment or priority channels?
- How do you currently handle large volumes of low-quality PRs (e.g., Hacktoberfest)?
Evidence
Locking 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.
If the Microsoft purchase of Github wasn't a good indicator of the start of the end, this is it, I know a lot of people like to have 'control' over things, but I have found so many fixes for software I use in un-merged PRs. Github moving towards closer and a closer system is good opp for alternatives to take some of that space. Nice.
I think OSS maintainers can protect themselves from hacktoberfest PR slop! A welcome change.
couldve simply put it behind a priority paywall, get money for work & showcasing or incorporating a piece of work, everyone is always free to fork but wanting to contribute to a popular project should be allowed for some money as well for good support
Disclaimer: this card is distilled by AI from community discussions as “pain point evidence”. It is a starting point for need analysis and validation, not a “validated market need”. AI has analytical limits; please open the original discussion above to manually verify before key decisions.