Do not reset robots.txt on upgrade
Do not reset customized robots.txt on Gitlab upgrades
We deploy our own robots.txt to block all crawling of our Gitlab. After each upgrade we need redeploy the robots.txt because the update resets it to your default.
It would be create if either:
- a customized robots.txt wouldn't be resetted on Gitlab upgrades
- there would be a place for a custom robots.txt which gets used if it exists.