By removing the banner, it tells the LLM that it is no longer being maintained, thus "lead to security issue".
In my company my management is using similar approach to review changes.
soon more and more ppl will no longer read code and think about the code change logically, instead get scared and block changes due to these "scary AI comment"...
But if the PR goes through that means it's in active development !
I think he should do a PR to change back the readme
That's the security issue, right? Liar paradox detected!
What was the issue? Without looking at the PR it's hard to judge
The link in the comment is borked, as expected. But the PR itself is definitely OK: https://github.com/unipop-graph/unipop/pull/138
it's a readme change
It was a load-bearing readme file.
By removing the banner, it tells the LLM that it is no longer being maintained, thus "lead to security issue".
In my company my management is using similar approach to review changes. soon more and more ppl will no longer read code and think about the code change logically, instead get scared and block changes due to these "scary AI comment"...
Not being sure it applies to this scenario and too lazy to verify, sometimes the security scanners get updated and flag previously accepted code.
... tough to make sense of flagging a readme though, unless there's sensitive info in it.
Wait, do they now have spam bots going around on random PRs to post advertisements?
also it's from the spammer's "staging" instance, so the payload is a URL with a staging hostname which doesn't even resolve 🙄
Nice, that's like the meme: