Laravel Closes GitHub Issues on Most Packages, Wants PRs Instead
Taylor Otwell has disabled GitHub Issues on most Laravel open-source packages, asking users to describe bugs to a coding agent and submit pull requests instead.
The main Laravel repository is unaffected. Symfony is experimenting with the opposite approach.
Taylor Otwell announced on X that he disabled GitHub Issues on most Laravel open-source packages last week. The change does not affect the main Laravel repository itself.
Instead of filing an issue, Otwell tells users to explain the bug to a coding agent and submit a pull request. Imperfect code is fine, he says, since it can be iterated on, and the PR still documents the problem even if a proper fix follows later. He expects most open-source libraries to operate this way soon.
Laravel News author Eric L. Barnes notes he initially skipped the story because it seemed minor, but online reaction proved otherwise. He points out that other PHP projects are moving in the opposite direction: Symfony is experimenting with an issue-first model where only issues are allowed and maintainers or their AI tools write the fixes. Both directions suggest maintainers feel burdened by the current contribution flow.
Barnes frames the move as typical of Laravel's willingness to change established habits, and notes the reversal would be trivial: if the experiment fails, issues can simply be turned back on.
Readers’ Forum
No contributions yet — open the debate.
Open the discussion
No account or password needed — just enter your e-mail and we’ll send you a one-time sign-in link. First time here? You’re set up automatically.
Your rating will be applied automatically after you sign in.
Check your inbox
We’ve sent a sign-in link to …. Open it on this device — this tab will sign you in automatically.
Nothing arrived? Check your spam folder — and mark the mail as "Not spam" so it lands in your inbox next time.