GitLabSec team-member here, ^ this 100%.
Our Trust and Safety team works really hard to keep up with spam. For those interested in how they do so, you can read more here[1]. We are also working on making our spam detection engine more effective at mitigating high-volume spam incidents such as this.
For current, working product improvements to detect and mitigate spam you and others can check out MRs labeled "spam fighting"[2]. We've had quite a few internal conversations about strategies and best-practices. For more information on how to contact our Trust & Safety Team, including tips on how to deal with abuse in your own instance or steps to suggest spam/abuse related features, see our handbook[3]
[1] https://about.gitlab.com/blog/2020/10/29/how-we-work-to-dete...
[2] https://gitlab.com/gitlab-org/gitlab/-/merge_requests?scope=...
[3] https://about.gitlab.com/handbook/engineering/security/secur....