On Fri, 16 Oct 2026 at 12:04, Daniel Sahlberg <[email protected]> wrote:
> A little late to the party but would it also make sense to add a > robots.txt file? I realise they work in slightly different ways. > [[[ > User-agent: * > Disallow: / > ]]] > > I would be nice too, but IMHO X-Robots-Tag is sufficient. With robots.txt we will have the same problem how to maintain the different robots.txt for different branches. Probably we can implement it via conditional Rewrite rule. > How about --record-only "merging" these differences in publish to > prevent accidental merge? (I saw the later SERVER_NAME commit but we > might prevent it from even appearing in publish). > > I thought about --record-only merge to block revision from merging to publish, but I think it would be error prone: 1. We will have to maintain record-only merge for any changes in 'subversion-staging' specific area in staging/.htaccess. 2. It will be easy to miss blocking such changes and accidently to apply "noindex, nofollow" change to publish. I am going to confirm with INFRA team that SERVER_NAME approach is proper solution and then test it on subversion.apache.org (publish). -- Ivan Zhakov
