@arnaudlevy @nomadami Would you consider it useful to also apply this logic to the workflow that builds the main branch, in order to check for broken links on the live website as well?
The alternative could be to build next from time to time and to use the checks there to correct the content in the system.
This comes together with considerations about Osuny reinstating its own workflow file, when it has been modified, as seen in 4e8d4582c8cdfacc637ecca42186ca0789c8aaab
In
6
I have exemplified how to run an automatic link checker on the generated static output of the Osuny site, scoped at
next
.Please see exemplary summary output of these jobs at:
@arnaudlevy @nomadami Would you consider it useful to also apply this logic to the workflow that builds the
main
branch, in order to check for broken links on the live website as well?The alternative could be to build
next
from time to time and to use the checks there to correct the content in the system.