@Shree That pattern looks like it's already caught by Pattern-matching website in answer and Pattern-matching website in body; append -force if you really want to do that.
[ SmokeDetector | MS ] Bad keyword in body, link at end of body, pattern-matching product name in body, pattern-matching website in body, potentially bad keyword in body (394): without any damage, it is useful by user880860 on askubuntu.com
that's the thing with working with spam filtering, eventually you find those cases that are right on the line, and you don't know whether to flag it, or to just let it be
@Shree That pattern looks like it's already caught by Pattern-matching website in answer and Pattern-matching website in body; append -force if you really want to do that.
@micsthepick Note that the very least I will do is delete one of the questions and put the user under surveillance. So some flag is certainly justified.
@tripleee That pattern looks like it's already caught by Pattern-matching website in answer and Pattern-matching website in body; append -force if you really want to do that.
Matt Hartley from GitHub support responded to my report about a couple of invalid PRs:
"Thanks for taking time to file the report. We're happy to take a look at the account in question. If we discover that GitHub's Terms of Service are being violated, we will take appropriate action."
"In the meantime, keep in mind that per the Hacktoberfest FAQ's, maintainers should tag any spam or irrelevant PRs with the "invalid" label to disqualify them."
@Makyen That pattern looks like it's already caught by Potentially bad keyword in body and Potentially bad keyword in answer; append -force if you really want to do that.
