No More Issues: Laravel Asks for PRs Instead
Laravel disabled issue creation on several package repositories — including Socialite and Scout — and now asks contributors to open pull requests instead; the main framework repo is unaffected. Brent Roose, an open source maintainer, walks through the trade-offs. Forcing a PR can cut maintainer triage time, and duplicate fix attempts are easier to close. But in the AI era, opening a PR is nearly as cheap as filing an issue, and LLM-written patches demand more review effort than ones a contributor reasoned through. Duplicate PRs also trigger far more CI runs than duplicate issues. Requiring PRs raises the contribution bar rather than lowering it, and shuts out contributors without AI access or enough experience — even though many people, the author included, started out writing Laravel issues. He draws no firm conclusion, but finds the change hard to square with the idea that every contribution is a learning opportunity. Aimed at OSS maintainers and contributors.