These things are done not to block pr done with the help of ai, but to block the ai slops pr, aka those never reviewed, fully vibecoded, and with the submitter that didn't understand anything about the problem or the code, just trusted claude.
The rule is general on purpose to allow the maintainer to freely remove whatever is very evident is just ai slop
exactly, I for example don't care usually about false positives, in the very uncommon case it happens the pr creator can discuss and prove he actually understood the problem, the codebase, the project policy and how to explain his solution actually could work.
How they enforce it in every other project with the same policy, if the reviewer/maintainer suspects the pr is ai slope he closes it. That's it, it works fantastically well, I do the same even in my job
As I said in another sibling post, you cannot strike that way. You have to follow procedures to organize a legit strike.
If I wrote an email like that not only my union would not protect me, they would most probably tell me the employer took the right decision because I put at risk other employees positions (if they followed my reccomandations to stop working just because I said it)
You can organize a strike BUT this is absolutely not the way you do it.
You have to follow strict procedures, work with your union and go into one or more formal negotiating tables with all the representatives of all the interested parts before even thinking about giving an ultimatum like that. And for sure you cannot communicate in that way using directly your work email
In her group email she also asked other employees to stop working in any other related project.
I mean, I don't see how google could NOT terminate her after such an event. I am in a nation with extremly strong worker protection law but that action alone would be enough to fire you on the spot.
The rule is general on purpose to allow the maintainer to freely remove whatever is very evident is just ai slop