Skip to content

Name the style registry the way the other hosts do - #19

Merged
barnumbirr merged 1 commit into
masterfrom
name-the-style-registry
Oct 6, 2026
Merged

barnumbirr merged 1 commit into
masterfrom
name-the-style-registry

Conversation

@barnumbirr

Copy link
Copy Markdown
Contributor

A comment in index.html and the padding check's failure message in scripts/check-site.sh referred to the style registry by a file name. Both now say "the estate style registry", the wording the other hosts' sources use.

Verification: scripts/check-site.sh passes, and a seeded padding change fails with the new message. Pinned shellcheck and actionlint pass. The apex's CSP allows inline styles without a hash, so a comment inside <style> cannot break it.

On merge: deploy-worker.yml redeploys the apex; the only served change is the comment text.

A comment in index.html and the padding check's failure message in
check-site.sh referred to the registry by a file name. Both now say "the
estate style registry", the wording the other hosts' sources use.

Comment and message text only: check-site.sh passes, and a seeded
padding change fails with the new message.
@barnumbirr
barnumbirr merged commit 2cbc60b into master Oct 6, 2026
1 check passed
@barnumbirr
barnumbirr deleted the name-the-style-registry branch October 6, 2026 20:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant