OK, so I came up with a small plan to at least make sure we don't put a site live without a menu.
Especially since in the multi-language version, the two menus seem to be independent; so the chance that you will put a website live with 2 working menus is now squared (e.g. if the chance was 0.8 in the Polish-only, it's not 0.64 -- and I think 0.8 is generous).
Please read through the individual commits (and not the squashed version below) to understand what is going on.
Basically we fail the build when there is no menu.
Then on netlify we (hopefully) retry up to 10 times to get a working build.
(and yes, it certainly happens that a build fails and a next hugo execution in a loop, only milliseconds later, same code, succeeds).
OK, so I came up with a small plan to at least make sure we don't put a site live without a menu.
Especially since in the multi-language version, the two menus seem to be independent; so the chance that you will put a website live with 2 working menus is now squared (e.g. if the chance was 0.8 in the Polish-only, it's not 0.64 -- and I think 0.8 is generous).
Please read through the individual commits (and not the squashed version below) to understand what is going on.
Basically we fail the build when there is no menu. Then on netlify we (hopefully) retry up to 10 times to get a working build.
(and yes, it certainly happens that a build fails and a next
hugoexecution in a loop, only milliseconds later, same code, succeeds).