-
Notifications
You must be signed in to change notification settings - Fork 100
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
Introduce GitHub Action to test resolvability of external links [DOC-253] #1382
Conversation
✅ Deploy Preview for hardcore-allen-f5257d ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
8e7bdb9
to
d21876c
Compare
d21876c
to
9f08bc4
Compare
9f08bc4
to
1f0d755
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed with workaround - 7a78108 Updated output - https://github.com/hazelcast/hz-docs/actions/runs/11907767488 |
Suggestion was to notify put on a cron schedule and have it notify a private @oliverhowell if you can send me a Slack webhook url for that channel I can do the rest. |
The test developed in hazelcast#1382 flagged multiple dead links. This PR fixes those _seperately_ to prove the status of the test. Note the changes from `install-hazelcast.adoc` ~~copy from~~ overlap with hazelcast#1355.
This PR adds an action that will, when a PR is opened, check the resolvability of any external links.
External links are defined as those using the
http
scheme - internal links between documentation is already covered by our existing dead links check.Action is deliberately modular to be be easily applied to other docs repos.
This runs whenever a PR is raised, which is sub-optimal because:
But the other alternative - a scheduled check - would have difficulty in knowing who to target a failure communication at to resolve the issues (other projects notify Slack channels, with varying degrees of responses).
An example of the output produced by this action can be found here.
Note that the external link check fails because of dead links, and won't pass until the following are addressed:
URL 'https://raw.github.com/olivernn/lunr.js/master/lunr.min.js' had status 404 (found in node_modules/lunr/index.html)
We should consider whether adding a check that we know will fail is a good idea - comparing the annoyance of a failing (non-blocking) test against the coverage that at least we can ensure things don't get worse.
Fixes: DOC-253