Closed rkdarst closed 2 years ago
The other builds (pdf/epub/etc) had more warnings, so I changed it to only fail on HTML errors.
I added the other builds when github actions was new as an experiment, I'm not sure if they are used much. I guess they don't need to be removed but we don't need to fail on them.
Hm, I think I would not do this. It can be made a separate action, so that deployment is not blocked if warnings fail. I think that may be better?
I agree it would be good to get some feedback during pull request review but it should not block deployment.
If a soft warning is enough (not blocking a green check), it should already be visible in the "Files changed" tab under any PR.
Seems like this is not needed... closing