If you want to run #GitLab with #CI - then spare yourself the pain and:
DO NOT LIMIT SIGN IN IP-ADDRESSES TO ONE!
The CI job impersonates the user account by a special token and immediately triggers the spambot protection. CI jobs fail: fatal: unable to access 'https://gitlab-ci-token:xxxxxxxxxxxxxxxxxxxx@example.org/tbr/test.git/': The requested URL returned error: 403
Also Your browser only gets a white page with zero content.
#selfpwn
@tbr Funny thing, there's at least one crypto exchange that does something somewhat similar. It makes note of your very complete exact IPv6 addrs and when it changes you need to do the whole song-and-dance re-auth.
Also given that this will be reachable via #IPv6 and in times of privacy extensions, I am not sure if I should leave this on _at all_.