-
Notifications
You must be signed in to change notification settings - Fork 389
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
Broken Link Checker - Github Action #354
Comments
My bad, I believe you are already using a github action that does just that. Could you please confirm if validate_links.yml check for broken links? |
The file you linked came from the original fork, and as we changed a few things around here, I'm not sure if it's working. |
After running the workflow, it found 101 broken links, How do you want to handle this @marcelscruz ? In my opinion, we will need to check that list and add all the "False Positive URLs" to the After running the workflow, this issue was created |
URLs added to |
yes
Sounds good to me |
Awesome, feel free to open a PR with whatever you have and I'll jump in asap. |
Fixes marcelscruz#354 - Add Workflow - Add ignore file - Add false positive urls to ignore file - Fix URL in readme - Delete broken links in readme - run tests
I put together a PR with all the changes in one commit. It run the test, but it did not create an issue with the RESULTS. |
Broken links checker workflow Fixes #354 - Add Workflow - Add ignore file - Add false positive urls to ignore file - Fix URL in readme - Delete broken links in readme - run tests
I believe that it will be a great idea to setup a GitHub action that runs periodically and checks for broken links.
It will check all repository links once per day and create an issue in case of errors.
Github action to check for broken links in Markdown, HTML, and text files using Lychee, a fast link checker written in Rust.
Here is a full example of a GitHub workflow file:
It will check all repository links once per day and create an issue in case of errors.
I'd like to share my experience with Lychee. I came across it yesterday and integrated it into my project. While it was helpful in identifying some broken links, it also generated some false positives (links that appear broken but function correctly). I'm still exploring the tool's functionality to potentially fine-tune its accuracy.
On a separate note, I encountered a permissions issue when trying to open new issues.
Project implementations:
here is an example from my own project:
I hope this helps
The text was updated successfully, but these errors were encountered: