Skip to content

docs: placeholder URLs that cannot resolve, instead of ones that 404 - #21

Merged
sotashimozono merged 1 commit into
mainfrom
docs/placeholder-urls-that-cannot-resolve
Sep 5, 2026
Merged

docs: placeholder URLs that cannot resolve, instead of ones that 404#21
sotashimozono merged 1 commit into
mainfrom
docs/placeholder-urls-that-cannot-resolve

Conversation

@sotashimozono

Copy link
Copy Markdown
Member

Closes #20.

Measured:

URL response
https://github.com/org/Pkg.jl/issues/12 404 — resolves, and fails
https://github.com/org/MyPackage.jl/issues/12 404
https://example.invalid/issues/12 000 — does not resolve, by design

The first two reach GitHub and come back 404, so a reviewer running a link checker sees two dead links — which is the finding that opened the review of another package in this organisation. example.invalid is reserved by RFC 2606 and cannot resolve, which is what a placeholder should look like.

The package's own tests already used it. Six sites in docs/src and src did not.

The lint does not use the network

A check that asks for a response would be a flake generator across three runners, and would fail on an offline build for a reason unrelated to the claim. The property is the host: a URL inside a fenced julia block must be under a reserved example domain, or on a host this organisation owns.

Control run — restoring one of the old URLs:

a URL in an example is a reserved placeholder or a host we own: Test Failed
   Evaluated: ["declaring.md: https://github.com/org/Pkg.jl/issues/12"] == String[]

Suite: 1022 passed.

🤖 Generated with Claude Code

Closes #20.

Measured:

  https://github.com/org/Pkg.jl/issues/12         404   resolves, and fails
  https://github.com/org/MyPackage.jl/issues/12   404
  https://example.invalid/issues/12               000   does not resolve, by design

The first two reach GitHub and come back 404, so a reviewer running a link checker sees two dead
links — which is the finding that opened the review of another package in this organisation.
`example.invalid` is reserved by RFC 2606 and cannot resolve, which is what a placeholder should
look like. The package's own tests already used it; six sites in `docs/src` and `src` did not.

The lint that keeps it that way does not use the network — a check that asks for a response would
be a flake generator across three runners. The property is the host: a URL inside a fenced julia
block must be under a reserved example domain or on a host this organisation owns. Verified by
restoring one of the old URLs and watching it fail, naming the file and the URL.

Suite: 1022 passed.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@sotashimozono sotashimozono self-assigned this Sep 5, 2026
@github-actions github-actions Bot added the documentation Improvements or additions to documentation label Sep 5, 2026
@github-actions

github-actions Bot commented Sep 5, 2026

Copy link
Copy Markdown
Contributor

📚 Docs preview: https://codes.sota-shimozono.com/ExperimentalAPI.jl/previews/PR21/

(updates on each push to this PR)

@codecov

codecov Bot commented Sep 5, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@sotashimozono
sotashimozono merged commit 0917523 into main Sep 5, 2026
14 checks passed
@sotashimozono
sotashimozono deleted the docs/placeholder-urls-that-cannot-resolve branch September 5, 2026 09:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Placeholder URLs in the documentation return 404

1 participant