Raised by cubic on glyphs#11 and locallingo#6: docs/app/assets/stylesheets/tailwind.sources.css is regenerated by bin/build-css on every build via bundle show, yet the sites commit it — so it churns with machine-specific absolute gem paths (/Users/<user>/.gem/ruby/<version>/...) on every rebuild by a different machine/Ruby, and the committed copy is a stale snapshot no build actually consumes (.dockerignore excludes it; every build path runs bin/build-css first).
Options:
- Gitignore it fleet-wide (like
app/assets/builds/*) — the install generator and --sync migration would add the ignore + git rm --cached.
- Keep committing it but write portable/relative globs so it stops churning.
Either way it's a docs-kit convention decision that should ship via the generator + a --sync migration, not per-site hand edits — which is why it was pushed back on in the two PRs above.
Raised by cubic on glyphs#11 and locallingo#6:
docs/app/assets/stylesheets/tailwind.sources.cssis regenerated bybin/build-csson every build viabundle show, yet the sites commit it — so it churns with machine-specific absolute gem paths (/Users/<user>/.gem/ruby/<version>/...) on every rebuild by a different machine/Ruby, and the committed copy is a stale snapshot no build actually consumes (.dockerignoreexcludes it; every build path runsbin/build-cssfirst).Options:
app/assets/builds/*) — the install generator and--syncmigration would add the ignore +git rm --cached.Either way it's a docs-kit convention decision that should ship via the generator + a
--syncmigration, not per-site hand edits — which is why it was pushed back on in the two PRs above.