-
-
Notifications
You must be signed in to change notification settings - Fork 556
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
[Feature] Add a broken link checker to the CI/CD pipeline #1521
Comments
👋🏻 @ericwbailey @p2635! Y'all still need help with this? Happy to take this issue if so |
I think it might be good to have a broken link checker. Probably once per month, or once in 6 months. I am curious if it creates one issue with all the broken link results or multiple? It might become a little spammy if it creates multiple issues. Also, the github repo for the above github action seems to have been archived and not maintained anymore. I personally would prefer something which is better maintained and not archived. |
I was looking around and this link checker seems superior to a lot of the others: https://github.com/lycheeverse/lychee.
|
I forked the a11y project and created an action for it, here is an example after an issue is automatically created: p2635#1. The action can be configured to run on a cron job, so that suits your requirements for once per month or once every 6 months @SaptakS. I noticed sometimes there are false positives though like https://midnight-lizard.org/home... more to be investigated. |
The false positives are definitely little concerning. Also, is the content of the automated issue created customisable? And can it also check that if there already exists an issue from before with the broken links? |
Thank you for suggesting a feature. Please fill out the following information:
Feature suggestion
Relates to my #1478 (comment). Potentially implement something like https://github.com/marketplace/actions/broken-link-checker-action to improve the process.
Terms
The text was updated successfully, but these errors were encountered: