Repository navigation
Verify Blocked Documentation Links With Public Probes - #41
Merged
Merged
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
PSchmiedmayer
force-pushed
the
feature/link-check-fallback
branch
from
October 12, 2026 21:31
ce9a6c0 to
4790994
Compare
There was a problem hiding this comment.
🟢 Approval recommended
The implementation is fail-closed where required, limits public disclosure, and includes comprehensive automated coverage.
0 open findings
What changed in this PR
Adds an opt-in Globalping fallback for Linkspector 403 responses while preserving strict handling for confirmed failures.
Changes:
- Adds secure public-probe verification and annotations.
- Adds unit and live regression coverage.
- Exposes and documents
globalping_hosts.
| File | Description |
|---|---|
README.md |
Documents fallback behavior and limits. |
actions/markdown-links/test_check_links.py |
Tests processing and regression behavior. |
actions/markdown-links/live_check.py |
Implements live regression verification. |
actions/markdown-links/check_links.py |
Processes reports and Globalping results. |
actions/markdown-links/action.yml |
Defines the shared composite action. |
.gitignore |
Ignores Python caches. |
.github/workflows/self-standards.yml |
Runs fallback unit tests. |
.github/workflows/repository-standards.yml |
Forwards the new input. |
.github/workflows/markdown-links.yml |
Uses the new shared action. |
.github/workflows/link-check-regressions.yml |
Adds scheduled and PR regression checks. |
.github/actionlint.yaml |
Permits self-repository action syntax. |
🧠 Review effort: Balanced
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
♻️ Current situation & Problem
The documentation checks in Grove #119 encounter HTTP 403 responses from Bluetooth and Zenodo, even though those pages are reachable from other networks. Ignoring the URLs would also hide future broken links.
⚙️ Release Notes
globalping_hoststo the Markdown Links and Repository Standards workflows. The fallback is disabled by default. For example:globalping_hosts: 'www.bluetooth.com,zenodo.org'.0.5.xrelease. Use the runner's installed Chrome and its sandbox configuration rather than downloading a separate browser build.📚 Documentation
The README documents configuration, limits, outcomes, and the live regression checks. Globalping measurements are public: only opt-in public documentation hosts are eligible, and URLs containing credentials, query strings, fragments, or nonstandard ports are not submitted. Reports are retained for seven days; findings use workflow annotations rather than PR comments.
✅ Testing
0.5.6. Bluetooth's initial 403 was verified through Globalping; a valid local document passed and the deliberately missing document still failed.main, and weekly. It runs the shared action against the four fixtures, asserts the expected broken-link failure, and separately requires verified live results for both public URLs. Inconclusive measurements fail this regression even though they are warnings in the reusable workflow.4790994.Code of Conduct & Contributing Guidelines