crofty 0.15.0 — a .gitignore on init, and a nudge for sites that lack one

A crofty site that you put under git init would commit things it shouldn’t: the built dist/, Hugo’s working dirs, and the theme cache crofty regenerates on every build.

Before

crofty init left it to you to write a .gitignore. If you forgot, the build output and the regenerated theme rode along into every commit.

After

crofty init now writes a minimal .gitignore for a fresh site. It ignores what crofty rebuilds — /dist/, /public/, /resources/, and /.crofty/themes/ — while keeping .crofty/config.json tracked, because the build needs it and it holds no secrets. An existing .gitignore (possible with crofty init .) is left untouched.

For a site you made before this, crofty build now prints a one-time hint when the folder is under git but has no .gitignore, showing the two lines to add. It only hints — it never writes the file itself, so what you track stays your choice.