PR spam today looks like email spam in the early 2000s
1–10 of 167 posts
Re: PR spam today looks like email spam in the early 2000s
#2Re: PR spam today looks like email spam in the early 2000s
#3I much prefer a blanket ban on PRs and issues created by AI agents (which is what I personally do for my repos; so far I have closed one[1]). In fact I would love a github alternative which considers AI contributions to be a breach of their terms of use and ban any people who let AI agents loose on their platform.
1: https://github.com/runarberg/markdown-it-math/pull/48#issuec...
Re: PR spam today looks like email spam in the early 2000s
#4Re: PR spam today looks like email spam in the early 2000s
#5Re: PR spam today looks like email spam in the early 2000s
#6In my main project we added a new requirement that all new contributors meet a maintainer in a non-textual format before their first PR is merged. Seems to work well for a small project.
Re: PR spam today looks like email spam in the early 2000s
#7Can I ask what the motive is to create agents to do this? Where is the profit?
Re: PR spam today looks like email spam in the early 2000s
#8Can I ask what the motive is to create agents to do this? Where is the profit?
Re: PR spam today looks like email spam in the early 2000s
#9Can I ask what the motive is to create agents to do this? Where is the profit?
I think there are a lot of “tech schools” overseas that require students to show proof of contribution to open source.
Could be used as a teaching experience that many maintainers would be happy to participate in, instead of feeling attacked with random low quality PRs.
Re: PR spam today looks like email spam in the early 2000s
#10Can I ask what the motive is to create agents to do this? Where is the profit?
I think there are a lot of “tech schools” overseas that require students to show proof of contribution to open source.