Taylor Disabled GitHub Issues on Laravel Packages | Mohamed Said [ ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MH.png) Mohamed Said Laravel Backend Engineer ](https://msaied.com) [ Home ](https://msaied.com) [ Projects ](https://msaied.com/projects) [ Articles ](https://msaied.com/articles) [ Certificates ](https://msaied.com/certificates) [ Contact ](https://msaied.com#contact-section) [ ](https://github.com/EG-Mohamed) [ Home ](https://msaied.com) [ Projects ](https://msaied.com/projects) [ Articles ](https://msaied.com/articles) [ Certificates ](https://msaied.com/certificates) [ Contact ](https://msaied.com#contact-section) [ home ](https://msaied.com) [ articles ](https://msaied.com/articles) Taylor Otwell Disabled GitHub Issues on Most Laravel Open-Source Packages On this page 1. [ Taylor Otwell Turns Off GitHub Issues on Laravel Packages ](#taylor-otwell-turns-off-github-issues-on-laravel-packages) 2. [ What Taylor Said ](#what-taylor-said) 3. [ How to Contribute a Bug Fix Under the New Workflow ](#how-to-contribute-a-bug-fix-under-the-new-workflow) 4. [ The Broader Open-Source Trend ](#the-broader-open-source-trend) 5. [ Key Takeaways ](#key-takeaways) 6. [ What This Means for Laravel Developers ](#what-this-means-for-laravel-developers) ![Taylor Otwell Disabled GitHub Issues on Most Laravel Open-Source Packages](https://cdn.msaied.com/632/d9612144281f22ce7b18e7ee82a2ea80.png) [ Laravel ](https://msaied.com/articles?category=laravel) [ Open Source ](https://msaied.com/articles?category=open-source) #Laravel #Open Source #GitHub #AI #Contributing #Taylor Otwell Taylor Otwell Disabled GitHub Issues on Most Laravel Open-Source Packages =========================================================================== 4 Sep 2026 3 min read ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MJ.jpg) Mohamed Said Table of contents 1. [ 01 Taylor Otwell Turns Off GitHub Issues on Laravel Packages ](#taylor-otwell-turns-off-github-issues-on-laravel-packages) 2. [ 02 What Taylor Said ](#what-taylor-said) 3. [ 03 How to Contribute a Bug Fix Under the New Workflow ](#how-to-contribute-a-bug-fix-under-the-new-workflow) 4. [ 04 The Broader Open-Source Trend ](#the-broader-open-source-trend) 5. [ 05 Key Takeaways ](#key-takeaways) 6. [ 06 What This Means for Laravel Developers ](#what-this-means-for-laravel-developers) Taylor Otwell Turns Off GitHub Issues on Laravel Packages --------------------------------------------------------- On September 4, 2026, Taylor Otwell announced via X that he had disabled GitHub Issues on most Laravel open-source packages. The move sparked a wave of discussion across the PHP and Laravel communities, even though — as Laravel News editor Eric L. Barnes noted — the change applies only to **packages**, not to the main Laravel framework repository itself. ### What Taylor Said In his own words: > Last week I disabled GitHub Issues on most Laravel open-source packages. > > If you hit a bug, describe it to a coding agent and open a PR. Even if the code isn't great, that's fine — code can be iterated on. The PR still documents the problem, and a proper fix can follow. > > I suspect this will soon be how most open-source libraries operate. The intent is clear: instead of filing a plain-text issue and waiting for a maintainer to act on it, contributors are expected to use an AI coding agent to produce at least a rough pull request that demonstrates the problem and attempts a fix. ### How to Contribute a Bug Fix Under the New Workflow The practical steps are straightforward: 1. **Reproduce the bug locally** in the relevant Laravel package. 2. **Describe the problem to a coding agent** (e.g., GitHub Copilot, Cursor, or any LLM-powered tool). 3. **Let the agent generate a patch**, even if it is imperfect. 4. **Open a pull request** — the PR itself becomes the documentation of the problem, and maintainers can iterate from there. There are no new CLI commands or configuration files involved; the change is purely a process shift. ### The Broader Open-Source Trend Interestingly, not every major PHP project is moving in the same direction. Symfony is experimenting with an *issue-first* model — contributors file issues, and then Symfony's own team or AI tooling writes the fixes. Both approaches share the same underlying motivation: **maintainer burnout from triaging a high volume of issues**. The two strategies just differ on who does the initial coding work: - **Laravel approach** — contributor uses an AI agent to draft a PR. - **Symfony approach** — contributor files an issue; project team or AI handles the code. ### Key Takeaways - GitHub Issues are disabled on most Laravel **packages**; the main `laravel/framework` repository is unaffected. - Bug reporters are now expected to open a pull request, ideally assisted by a coding agent. - Imperfect PRs are explicitly welcome — they document the problem and give maintainers something concrete to iterate on. - Symfony is taking the opposite approach, keeping issues open and having maintainers or AI write the fixes. - The change is reversible; if it does not work out, issues can simply be re-enabled. - AI-assisted contribution workflows are becoming a real expectation in open-source maintenance, not just a novelty. ### What This Means for Laravel Developers If you rely on a Laravel package and hit a bug, your first move should now be to reach for your preferred coding agent rather than the "New Issue" button. The barrier to contributing has arguably lowered — you do not need a perfect fix, just a PR that captures the problem. That is a reasonable trade-off that keeps maintainers focused on reviewing code rather than triaging text. Whether this model spreads across the wider PHP ecosystem remains to be seen, but the direction of travel is clear: AI is becoming a first-class part of the open-source contribution loop. --- *Source: [Laravel News — Taylor disabled GitHub Issues on most Laravel open-source packages](https://laravel-news.com/taylor-disabled-github-issues)* Found this useful? [ ](https://twitter.com/intent/tweet?url=https%3A%2F%2Fmsaied.com%2Farticles%2Ftaylor-otwell-disabled-github-issues-on-most-laravel-open-source-packages&text=Taylor+Otwell+Disabled+GitHub+Issues+on+Most+Laravel+Open-Source+Packages) [ ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fmsaied.com%2Farticles%2Ftaylor-otwell-disabled-github-issues-on-most-laravel-open-source-packages) Frequently Asked Questions ---------------------------- 3 questions Q01 Did Taylor Otwell disable GitHub Issues on the main Laravel framework repository? No. The change applies only to most Laravel open-source packages. The main laravel/framework repository still has GitHub Issues enabled. Q02 How should I report a bug in a Laravel package now that Issues are disabled? Describe the bug to an AI coding agent, let it generate a patch, and open a pull request against the package. Even an imperfect PR is acceptable — it documents the problem and gives maintainers something concrete to work from. Q03 Is the Laravel approach the same as what Symfony is doing? No. Symfony is experimenting with an issue-first model where contributors file issues and the project team or AI writes the fixes. Laravel is doing the opposite: disabling issues and asking contributors to submit AI-assisted pull requests directly. Continue reading More Articles --------------- [ View all ](https://msaied.com/articles) [ ![Exclude Vendor and Default Commands in php artisan dev (Laravel 13.30)](https://cdn.msaied.com/631/ba9b50ef4b7355a32c378f404d978b90.png) Laravel Artisan Laravel 13.30 ### Exclude Vendor and Default Commands in php artisan dev (Laravel 13.30) Laravel 13.30 adds withoutVendorCommands() and withoutDefaultCommands() to the DevCommands class, giving you p... ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MJ.jpg) Mohamed Said 4 Sep 2026 3 min read Read ](https://msaied.com/articles/exclude-vendor-and-default-commands-in-php-artisan-dev-laravel-1330) [ ![Laravel August 2026 Product Updates: Framework, Cloud, and Forge](https://cdn.msaied.com/630/37bf960d82f877f3063ffe9d11fa3c7b.png) Laravel Laravel Cloud Laravel Forge ### Laravel August 2026 Product Updates: Framework, Cloud, and Forge Laravel's August 2026 updates bring read-through filesystems, Turbopuffer semantic search in Scout, rebuilt ma... ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MJ.jpg) Mohamed Said 3 Sep 2026 3 min read Read ](https://msaied.com/articles/laravel-august-2026-product-updates-framework-cloud-and-forge) [ ![Laravel queue:work Now Prints Why the Worker Stopped](https://cdn.msaied.com/629/bed93940d17b932032d64cee2e32d333.png) Laravel Queue Laravel 13.30 ### Laravel queue:work Now Prints Why the Worker Stopped Laravel 13.30 adds a stop-reason line to queue:work output. Workers now print why they exited—memory limit, re... ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MJ.jpg) Mohamed Said 3 Sep 2026 3 min read Read ](https://msaied.com/articles/laravel-queuework-now-prints-why-the-worker-stopped) [ ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MH.png) Mohamed Said Laravel Backend Engineer ](https://msaied.com)Senior Backend Engineer specializing in Laravel, scalable SaaS platforms, APIs, and cloud infrastructure. I build secure, high-performance web applications that help businesses grow. Explore - [Home](https://msaied.com) - [Projects](https://msaied.com/projects) - [Articles](https://msaied.com/articles) - [Certificates](https://msaied.com/certificates) - [Contact](https://msaied.com#contact-section) Connect - [ hello@msaied.com ](mailto:hello@msaied.com) - [ +20 109 461 9204 ](tel:+201094619204) © 2026 Mohamed Said. All rights reserved. [ ](https://github.com/EG-Mohamed) [ ](https://www.linkedin.com/in/msaiedm/) [ ](https://wa.me/201094619204) [ ](mailto:hello@msaied.com) [ ](https://drive.google.com/file/u/0/d/1MF20IPRJyzfy32mhEutjL5EpSls0w2Q8/view)