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
Automatioc check for broken links in documentation #6208
Comments
I was running docs.lvgl.io through a dead link checker website. It stopped after 2000 checks and found 367 dead links. Most of them are coming from the Of course there where some good findings too. With a script we can have a good control about what to check and what not. E.g. do not go to back to |
They used to all work. I know there were changes made to that part of the documentation generation when the MicroPython stuff was removed. IDK what was done when that happened. I am going to have to go back into the commits and dig out the old code that got changed.... |
checking links is not that hard to do and it is able to be done at the documentation generation level by doing a recursive check against the generated HTML output using regex to collect the links and then using Python requests to see if the link works. This is able to be done using threads and have each thread check like 20 links. I can also spread it out across the available cores as well. |
Both are cool! Thanks! If you already know how to approach it, please open a PR. |
Problem to solve
As seen in #6207, some links can become outdated in the docs / repo over time.
The goal is to detect and report them automatically.
Success criteria
CI/CD checks for broken links
Solution outline
Rabbit holes
http(s)
) or have esoteric format due to the "rich-text context" they are later processed inTesting
TODO
Teaching
Internal tool, not needed
The text was updated successfully, but these errors were encountered: