crofty 0.16.0 — catch a theme cache that git would commit
crofty regenerates its theme under .crofty/themes/ on every build. If git
tracks that folder, it gets committed and churns your history each time you
build.
Before
The build hinted about .gitignore only when the file was missing entirely. A
site that had a .gitignore without the /.crofty/themes/ rule was missed — so
the regenerated theme kept getting committed with no warning.
After
crofty build now asks git what it actually ignores, not just whether a
.gitignore exists, and tells you what to do:
- if the theme is already committed, it shows
git rm -r --cached .crofty/themes/plus the line to add to.gitignore - if it’s simply not ignored yet, it shows the line to add
- if git already ignores it (or the site isn’t in git), it stays quiet
It only ever hints. It never edits .gitignore or touches git for you, and
.crofty/config.json stays tracked — the build needs it and it holds no
secrets.