Verify official GitHub targets during page service errors - #27
Merged
Merged
Conversation
showxu
changed the title
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
1 participant
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.
Website verification can fail when GitHub's HTML pages return server errors for existing public targets. Keep HTTP checks with bounded retries and concurrency; for official GitHub links that still return 5xx, verify the repository and exact file, directory, release or security-policy target through the authoritative API. Client errors, missing or private targets, unsupported routes and failed API checks remain failures.
Workflow tokens are used only for read-only API requests by the link validator. Authentication is optional for local public API checks, and API redirects fail rather than forwarding credentials.
Validation:
npm ci,npm run test:install, andnpm run checkpassed, including desktop/mobile smoke and accessibility checks. Nine link-validation tests cover missing files, target types, public repository identity, client errors, unsupported routes, stable releases, request reuse and credential isolation.