Skip to content

NO-JIRA: Hack&Hustle - markdown link checker script and report#16363

Draft
fsgreco wants to merge 2 commits intoopenshift:mainfrom
fsgreco:hacknhustle-april-script-md-links
Draft

NO-JIRA: Hack&Hustle - markdown link checker script and report#16363
fsgreco wants to merge 2 commits intoopenshift:mainfrom
fsgreco:hacknhustle-april-script-md-links

Conversation

@fsgreco
Copy link
Copy Markdown
Contributor

@fsgreco fsgreco commented Apr 28, 2026

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 curl whether the link reports a status code other than 200.

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

fsgreco and others added 2 commits April 28, 2026 12:53
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>
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 28, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

@fsgreco: This pull request explicitly references no jira issue.

Details

In response to this:

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 curl whether the link reports a status code other than 200.

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

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.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 28, 2026

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@openshift-ci openshift-ci Bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 28, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Apr 28, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: fsgreco
Once this PR has been reviewed and has the lgtm label, please assign jhadvig for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants