pagehas

Overview ¶

Command pagehas checks a PUBLISHED page: that it answers 200, and that it carries each of the texts it is given.

pagehas https://go-images.github.io/docs/en/modules/ "Fuzzed since v0.13.8"

WHY IT EXISTS ¶

The rule here is that a change a user can see is finished when the README, the landing and the docs say so, AND the published page has been looked at: HTTP 200 and the new text present, not only a green merge. A merge says the source changed; a deploy says a workflow ran. Neither says what a reader is served, and both have been green while the page was not:

• 2026-10-18, go-simd: a landing link to /docs/repos/highway/ was merged and deployed, and answered 404, because mike serves the docs under /docs/latest/. Only fetching the page showed it.
• the same day, go-images/docs: the Pages build was still running when the deploy workflow reported success, and the page served the old text for a minute longer. A check that ends at the workflow cannot see that.

That check was retyped, slightly differently, in a scratchpad every time it was needed, and lost with the scratchpad. It lives here now.

WHAT IT REFUSES TO SAY ¶

⛔ A page that could not be read is not a page without the text. A timeout, a 404 or a body cut off at the size limit is reported as what it is, with its own exit status, so "the text is missing" is only ever said about a page that was read whole.

⛔ A CDN may serve a cached page for minutes after a deploy. --fresh adds a query string that the cache has not seen, so the answer comes from the origin; without it the answer is what a reader gets right now, which is also worth knowing. The report says which was asked.