Taylor on X:
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.
I didn't cover this originally because I didn't think it was that big of a deal, but the internet seemed to have other plans. Also, this is just for packages, not the main Laravel repo itself.
Apparently, other PHP projects are going in the opposite direction: they only allow issues, then take them and have their own AI or devs write the fixes. So project maintainers everywhere are feeling burdened by the current flow.
Either way, I think the future is coming fast, and the way we've always done stuff is changing; for better or worse, AI is taking a much bigger role in our lives. Just because something has been the same for years doesn't mean you can't adapt and push forward. That is what Taylor and Laravel have always done, and this is just another example.
If this change doesn't work, so what? Turn the issues back on.
