CRITICAL: Chinese guys are polluting GitHub issues on an unprecedented scale #191040
-
Discussion TypeGeneral Discussion ContentChinese guys are polluting GitHub issues, newly created accounts are batch creating gambling and illegal issues on various popular repos. For real-time status, visit: https://github.com/issues?q=is%3Aissue%20state%3Aopen%20archived%3Afalse%20sort%3Aupdated-desc trim.89D1D51B-A48D-4EB4-8770-6570D82C3121.MOV |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 2 replies
-
|
@matthewisabel Please be aware of this. |
Beta Was this translation helpful? Give feedback.
-
|
Try creating a support ticket and/or if these are your repositories, create or find a GitHub bot to moderate issues, and delete if nonsensical. |
Beta Was this translation helpful? Give feedback.
-
|
As a developer from China, I regret this situation, but please know that we stand on the same side as you—we love the open source community and hate spam. We feel sorry for certain bad actors in our country who cannot represent all Chinese developers. Please continue to trust us; we believe the spam problem will ultimately be resolved. also see: https://github.com/isce-framework/isce2/issues/26661 |
Beta Was this translation helpful? Give feedback.
-
|
I can see the problem in the frustration of going through. Please know that this is an issue that would not last for long and as the developer that has commented just right above me @wu-mx said , those bad actors do not represent the full margin of the Chinese community. I am indeed, very surprised and shocked by the situation as well, what this means that Github would require to make more defensive measures to avoid spams to such repositories, and ensure that maintainability is clear and engageable by all committee members from all different origins. |
Beta Was this translation helpful? Give feedback.
-
|
Looks like the issue was fixed by GitHub and the maintainers, closing as resolved. |
Beta Was this translation helpful? Give feedback.
Looks like the issue was fixed by GitHub and the maintainers, closing as resolved.