Problem
shardmind adopt/update writes .shardmind/logs/bootstrap.log (and presumably other hook logs). The template's .gitignore doesn't cover .shardmind/logs/, so every managed install will commit its local runtime hook output — not vault config, not portable, pure noise in history.
Confirmed live: after an adopt, git check-ignore .shardmind/logs/bootstrap.log returned non-ignored → it would have been staged.
Fix
Add to the template .gitignore:
# ShardMind runtime logs (local hook output, not vault config)
.shardmind/logs/
(Already patched locally in the affected vault; this is the template-side fix so every install inherits it.)
Related
Problem
shardmind adopt/updatewrites.shardmind/logs/bootstrap.log(and presumably other hook logs). The template's.gitignoredoesn't cover.shardmind/logs/, so every managed install will commit its local runtime hook output — not vault config, not portable, pure noise in history.Confirmed live: after an adopt,
git check-ignore .shardmind/logs/bootstrap.logreturned non-ignored → it would have been staged.Fix
Add to the template
.gitignore:(Already patched locally in the affected vault; this is the template-side fix so every install inherits it.)
Related