Journal: one file per entry in log/; drop merge=union #2
Loading…
Reference in a new issue
No description provided.
Delete branch "log-per-entry"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Implements the proposal from #1, with three deltas argued in review:
log/from the index/orphan/link/source checks (likeraw/) instead of frontmatter-checking entries — pages get merged/split/deleted legitimately, so checking historical targets would generate perpetual noise. The one new deterministic check is filename format (LOG-FORMAT:).cat wiki/log/*.mdreads exactly like the old journal.log/<today>-init-wiki.mdwhen the journal is empty, and the session-start hook derives last-update from the newest entry filename (legacylog.mdfallback for pre-migration repos).Also per the issue: template ships
log/instead oflog.md; the.gitattributesfragment is gone entirely (union was its only line — existing repos keep a harmless leftover, or delete the line); existinglog.mdfiles stay as read-only history — no entry splitting.One honest nuance on failure mode 1: GitHub definitely ignores merge drivers in PR mergeability, but Forgejo merges via real git and may honor in-tree
merge=union; the claim is strongest for GitHub-hosted adopters and local rebases. Failure mode 2 (silent resurrection) held everywhere and justifies the change on its own.Suite: 93 asserts green (was 85). Migration for adopters: pull the kit, re-run
install.sh(machinery + docs refresh; a dated init entry is seeded only iflog/is empty), keeplog.mdas history, optionally delete themerge=unionline from.gitattributes.log.md+merge=unionwith one file per entry #1