I guess also AI managed canary l releases could be an option IMHO that combine open PRs.
I came from the "free software as in free puppy" camp. I would stop by to play with the puppy, but I won't feed it.
I guess if I do the same today, I might submit a better-than-band-aid fix from LLM. You would probably think I am not a real user.
I had multiple PRs for entirely hallucinated problems.
Or where no human ever looked at project or PR and were just attacking open source projects with spam PRs pretending to be contributions. Not sure whether it was out of malice or done for some other reason. Maybe they were mistakenly thinking it is helpful?
I believe a fair bit of this is an attempt to gain numbers where quantifiable numbers are advertised on otherwise indistinguishable resumes (with the corresponding belief that those numbers make differences in filtering or hiring decisions).
I base that on having seen people in the days of old put their Stack Overflow reputation on resumes thinking that having a rep of 4321 will be more likely hired than someone with a rep of 1234.
Having "210 accepted PRs on GitHub" (they believe) would appear to make them a more productive / less risky hire than someone who hasn't done any.
---
This is really a case of indistinguishable resumes where nearly everyone in the pool went to the same college, same internships, same capstone project, and maybe the same first year or two of professional experience.
I could see it as a "proof of familiarity with CI and expectations for a PR", though for applicants that are spamming the process with poor PRs (and people posting poor Q&A on Stack Overflow back in the day), this often hurts them more than it helps as its a demonstration of what they are going to be doing if they are hired (I've already got too many poor quality PRs to review, your PRs would not reduce the amount of time that the reviewer would need to spend).
So yeah, I've considered it and eliminated it for most PRs we used to get. Because no, a 2nd year student in university did not run into an obscure edge case in production that none of my 1M+ QPS users did.