Documentation
¶
Overview ¶
Command pagetext says whether a PUBLISHED page contains the text we wrote:
pagetext [flags] URL want... [-- URL want...]
It is the last step of "every user-visible change updates the README, the landing page and the docs, and the published page is checked". It is not pagescheck, which asks whether a Pages site serves what its repository builds.
⛔ The first check after a deploy said the new text was MISSING. It was not: GitHub Pages' CDN was still serving the previous build, and the same URL with a cache-busting query showed the text. A shared cache keys a response on the target URI, query included (RFC 9111, section 2), so a changed query string is a different entry and reaches the origin. So a query parameter is added by default (-no-cache-bust turns it off), and -retry N -wait D polls, bounded, until the deploy is visible.
The match is on the page's TEXT: Hugo escapes and minifies, so "--output" can be split by tags or written with entities. -raw matches the bytes instead.
Reading a page is not a GitHub API call and costs nothing against the budget Renovate shares.
Source Files