This giant batch of PRs came as a bit of a surprise. It’s great to see folks making direct contributions like this, but in the past, we’ve strongly encouraged discussing things here first, before encouraging people to put effort into things that may not be a great fit.
Our systems aren’t designed for this kind of thing. Pull requests do consume resources, both in terms of machine time and attention.
With the effort bar getting lower, I suppose we need to think about where to introduce some additional helpful friction into the process, without making it too much of a burden for contributors or maintainers.
It’s not something we’ve encountered before, so I’m not coming here with a clear set of guidelines yet (and I’m not really the right person to be establishing them). I’ll let someone on our team who is closer to problem share more of their thoughts on this in when they get a chance.
Some of these may be great, but we’ll need to figure out how best to evaluate that with you.
Just wanted to jump in first and share this first in case you see them get closed or labeled in advance of that and are wondering why.