Closed github-actions[bot] closed 2 years ago
Well, I guess this answers our question! No, the link checker is not set up correctly.
There's a few different things going on here:
Cannot find file file:///github/workspace/tutorials/...
. This should be easy to fix, by setting --base https://napari.org
HTTP status client error (429 Too Many Requests) for url (https://github.com/...
. The solution here should be adding our github token as an argument to the lychee call --github-token <github-token>
http://localhost:8080/
is a localhost address, actions/checkout@v2.3.3
is not a link, and https://github.com/orgs/napari/teams/core-devs
is not accessible to anyone outside the core dev team). There are some --exclude
options for lychee that we should be able to use to fix this.Summarizing:
There are a lot of broken links caused by files that have been renamed or moved. I'm tempted to just let @melissawm re-organise everything first, before we go through and fix all the links one by one https://github.com/napari/napari/issues/3390
Yes - I'm actually going through some of the files and fixing those as I go, trying to get the sphinx errors and warnings down :)
Josh says that we need to set the user agent to fix the 403 forbidden errors with image.sc - https://forum.image.sc/t/how-to-check-for-broken-links-pointing-to-image-sc/58688/2
Lychee has a --user-agent
flag you can set.
We'll need something like --user-agent "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:93.0) Gecko/20100101 Firefox/93.0"
Closing this in favour of newer link checking reports.
Ideally https://github.com/napari/napari.github.io/pull/273 will have fixed any remaining lychee configuration issues - we'll see how well that's actually working next week.
Errors were reported while checking the availability of links.
Full Github Actions output