Commit fe64639
ci: fail PRs when committed Tailwind/Font Awesome assets are stale
Deploys ship the committed, purged CSS and subsetted webfonts as-is
(bare hugo, not the build:* scripts), so a markup/content change that
adds a Tailwind class or fa-* icon silently renders wrong until someone
regenerates them — exactly how w-auto slipped through.
Add a freshness check to the PR build: regenerate via build:css and
build:icons, then fail if assets/css/tailwind.css or
assets/css/fontawesome-subset.css differ from what is committed, with a
message telling the dev to regenerate and commit. Diffs the generated
CSS (deterministic, the source of truth for included classes/icons)
rather than the woff2 bytes, which vary across subset-font versions.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>1 parent 66c25e7 commit fe64639
1 file changed
Lines changed: 19 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
68 | 68 | | |
69 | 69 | | |
70 | 70 | | |
| 71 | + | |
| 72 | + | |
| 73 | + | |
| 74 | + | |
| 75 | + | |
| 76 | + | |
| 77 | + | |
| 78 | + | |
| 79 | + | |
| 80 | + | |
| 81 | + | |
| 82 | + | |
| 83 | + | |
| 84 | + | |
| 85 | + | |
| 86 | + | |
| 87 | + | |
| 88 | + | |
| 89 | + | |
71 | 90 | | |
72 | 91 | | |
73 | 92 | | |
| |||
0 commit comments