This is an automated archive made by the Lemmit Bot.
The original was posted on /r/opensource by /u/Frosty-Protection-53 on 2025-08-29 16:24:50+00:00.
Maintaining an open source project and getting 10-15 PRs weekly from contributors ranging from complete beginners to senior engineers. The quality variance is insane.
Some PRs are production-ready, others introduce bugs that would crash the entire system. I spend more time reviewing and providing feedback than actually working on features. It’s becoming unsustainable as a volunteer effort. The challenge is being educational without being discouraging. Want to help beginners learn but also need to maintain project quality. Can’t just auto-reject low-quality PRs but can’t merge everything either. Started using greptile to do initial screening and provide consistent feedback formatting. Helps catch obvious issues and gives me a starting point for more detailed reviews. Still working on finding the right balance between automation and human mentoring.
How do other maintainers handle this? What’s your process for managing PR quality at scale while staying welcoming to new contributors?