-
-
Notifications
You must be signed in to change notification settings - Fork 359
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
Find and fix broken/dead links #54
Comments
I would like to work on this,may I take this issue???? |
Great sure you can work on this issue, this is a recurring/open issue so best you use the instructions/tips placed in this issue to generate the deadlines and fix them and create a new PR for it - how does that sound? |
Ya will do that!! |
Please read the description of the issue, it outlines it all. Step by step and systematically, if you don't follow it please ask me then. |
As see from #53 we can have broken/dead links, links that once worked can be unavailable for reasons outside the control of this project/repo!
Hence I have decided to manually scan (for now) the repo from time to time for such links and fix them - if there is one. Here are the steps to take:
New broken/dead links
markdown-link-check
(see https://www.npmjs.com/package/markdown-link-check to find out how to install and use it)Existing broken/dead links across the repo
Existing dead/broken links are marked with the '[deadlink]' marker.
As part of this issue, fixing these links is also helpful - although if they are left in there it's cause their fix wasn't immediately available or found on searching on the relevant sources.
Eventually, we can automate the task of finding such links via a GitHub action during GitHub events like commit, push or pull request creation.
The text was updated successfully, but these errors were encountered: