Build artifacts are an unbounded URL space; AI and search crawlers walked
them in full on vm4006 (1.9 GB in a week) and answered 404 on /robots.txt.
Served by Werkator itself so every proxy in front of it delivers it without
a host-level file that a regenerated .htaccess could lose.
Build artifacts are an unbounded URL space; AI and search crawlers walked
them in full on vm4006 (1.9 GB in a week) and answered 404 on /robots.txt.
Served by Werkator itself so every proxy in front of it delivers it without
a host-level file that a regenerated .htaccess could lose.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Build artifacts are an unbounded URL space; AI and search crawlers walked
them in full on vm4006 (1.9 GB in a week) and answered 404 on /robots.txt.
Served by Werkator itself so every proxy in front of it delivers it without
a host-level file that a regenerated .htaccess could lose.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Build artifacts are an unbounded URL space; AI and search crawlers walked
them in full on vm4006 (1.9 GB in a week) and answered 404 on /robots.txt.
Served by Werkator itself so every proxy in front of it delivers it without
a host-level file that a regenerated .htaccess could lose.
Co-Authored-By: Claude Fable 5.1 noreply@anthropic.com
Pull request closed