-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
link-checker fails with relative URLs #86
Comments
@marcoscaceres This appears to be a limitation of 'link-checker' npm package, as it expects a base directory instead of a file. Maybe we can skip |
Before I started using w3c/spec-prod, I worked with lycheeverse/lychee-action for doing link checks. It wasn't perfect, either, but did have some options and patterns to limit the links it would follow: json-ld/json-ld-star@0c9b640#diff-b803fcb7f17ed9235f1e5cb1fcd2f5d3b2838429d4368ae4c57ce4436577f03f |
@gkellogg Thanks for introducing me to lychee. I'll try it out, and if it doesn't work well enough, I'll fix href-checker. Maybe this weekend. |
Is there a workaround, perhaps to just skip the link checker? It's interfering with various update processes. |
Link checker is currently opt-in, so you can skip the link checker by removing |
Using w3c/spec-prod@v2
See https://github.com/w3c/N3/runs/2793542809?check_suite_focus=true for example, but also failing in https://github.com/w3c/rdf-star/runs/2810861457?check_suite_focus=true.
Both specs contain an href to a file relative to the spec source, and link-checker fails on them.
From https://github.com/w3c/N3/runs/2793542809?check_suite_focus=true
From https://github.com/w3c/rdf-star/runs/2810861457?check_suite_focus=true:
cc/ @pchampin @william-vw
The text was updated successfully, but these errors were encountered: