NO-JIRA: Hack&Hustle - markdown link checker script and report#16363
NO-JIRA: Hack&Hustle - markdown link checker script and report#16363fsgreco wants to merge 2 commits intoopenshift:mainfrom
Conversation
Improve docs link quality checks by adding a new contrib script to scan markdown files for URL issues and write problems (404s, errors, redirects) to a CSV report for manual revision. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
|
@fsgreco: This pull request explicitly references no jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
Skipping CI for Draft Pull Request. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: fsgreco The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
As part of my Hack & Hustle exploration, I added a new contrib script to scan Markdown files for URL issues and write identified problems (404s, errors, redirects) to a CSV report. This improves the quality of documentation links.
Analysis / Root cause:
The idea originated while working on #16362; links inside Markdown guidelines can become deprecated, broken, or modified over time.
Solution description:
This script simply iterates through every external link inside a Markdown file and quickly checks via
curlwhether the link reports a status code other than200.It requires human supervision at the end in order to decide whether a redirect is acceptable or not, or to find the replacement link in case the old one is broken. Hence, the CSV artifact is useful for manual review, whether run on a CI or locally.
Reviewers and assignees:
Docs approver:
/assign @Leo6Leo