Closed lwasser closed 3 months ago
This actually works ✨ but
there may be a way to caption that information however in the terminal - it works locally just not in the action. nothing gets written out in the action for some reason.
I like this approach. I will give it a look on Monday re: output.
You may also want to try this action: https://github.com/anishathalye/proof-html
It seems better maintained than what we had and is used by a few thousand folks.
@willingc thank you i can't figure this out. The approach i implmeneted works well - i've tested it locally in all scenarios. it ignores new files but finds broken links in them. it looks for alt tags and other html issues. but the only way to see the output when it fails it so view the raw logs.
i'm so confused by this because locally the output in the terminal is there. so this is a ci specific issue that i don't yet understand.
that action looks nice but i worry it won't ignore new files similar to the action we have now. i could be wrong!!
oh it's a totally different tool! we should try that!! writing ruby code is not my favorite things to do 😆 And an pre-built action with a docker container will always be faster
@willingc actually i just encountered the SAME issue in a pr jesse opened with htmlproofer. so now i'm wondering if we should actually drop htmlproofer. i will open an issue however just in case the maintainer sees it (hasn't been updated since august)
I am going to merge this just to see how it does - especially knowing we have a new page i can test it on! i will revert if it is too slow / doesn't work as expected.
i'm trying to now run html proofer via a script to customize how it operates.