-
Notifications
You must be signed in to change notification settings - Fork 291
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
Fix all broken links #4476
Comments
Just fixed one in 814919d, probably several of this type:
|
@finanalyst - how long will it take for fixes to raku/doc/main to show up on the error report? |
@dontlaugh - can we get this error report running somewhere off our CI so we can force it to regen when doing fixing/testing? |
@coke sure thing. Just point me to the code and how to run it. Is it a standalone program? |
I'm assuming it's a config option in @finanalyst 's local build of the site. I'll dig. |
@finanalyst - it's been 3 weeks - how often is the error report regenerated on your site? |
@coke @dontlaugh Sorry, I missed the question to me - I guess it was when I wasn't fully functioning.
I have just created a PR to generate the error-report (it was being ignored during the build process). |
I will do a production deploy this evening so we can start collecting data. |
We should be working off https://docs-dev.raku.org/error-report or a locally generated version of this report now. |
See #4500 (now closed) |
Also use anchors-only if we're referring to the same document. Part of #4476
All issues resolved except for those issues covered in: |
See the error report on @finanalyst's copy of the doc site. This covers internal and external broken links, and this page should be blank.
The text was updated successfully, but these errors were encountered: