gitlab thinks issue contains spam

Summary

I tried to submit an issue to a project on gitlab.com that I own, and gitlab made me solve a captcha.

Steps to reproduce

Create an issue with the same content as sequoia-pgp/sequoia#160 (closed) and have it classified as spam.

What is the current bug behavior?

gitlab thinks this is spam.

What is the expected correct behavior?

gitlab creates an issue.

Output of checks

This bug happens on GitLab.com

Assignee Loading
Time tracking Loading