Taylor disabled GitHub Issues on most Laravel open-source packages.
Taylor Otwell announces the transition of Laravel's open-source issue trackers to GitHub Discussions, focusing maintainer time on reproducible pull requests and community collaboration.
Refocusing Open-Source Collaboration in the Laravel Community
In a blog post that generated widespread discussion across the software ecosystem, Taylor Otwell announced that GitHub Issues have been disabled across most primary Laravel open-source repositories.
The Motivation Behind the Change
As Laravel has grown to millions of active installations worldwide, issue trackers frequently became inundated with general support questions, configuration misunderstandings, and questions better suited for community forums. This high volume placed an unsustainable burden on core framework maintainers.
The New Collaboration Model
- GitHub Discussions: Questions, feature proposals, and open-ended technical ideas are now directed to repository GitHub Discussions.
- Pull Requests with Reproductions: Verified bug reports are welcomed directly as pull requests featuring failing Pest or PHPUnit tests.
- Dedicated Bug Triaging: Community contributors can collaborate on reproducing issues in Discussions before raising code fixes.
This transition ensures that core maintainers can spend their energy enhancing the framework, accelerating code reviews, and building the future of Laravel.