🌿 appendlog v1.0.0 · MIT
Append timestamped entries under a stable marker in long shared files — append-only, dedupe, zero dependencies.
The problem
Long shared files (plans, journals, state docs) edited by multiple actors break targeted edits: prose anchors get duplicated ("found 6 occurrences"), drift ("text not found"), and one bad edit can rewrite history. The fix is to make those files append-only: never touch existing content — only insert a new entry right after a stable marker comment such as <!-- LOG -->.
Guarantees
- Append-only — existing lines are never modified or reordered; a single line is inserted after the first marker occurrence.
- Dedupe — an identical entry already present → no-op (exit 0), not a second entry.
- Marker missing → clear error (exit 1), file untouched.
- Atomic-ish write — temp file +
os.replace. - Custom
--templateand--stamp-format,--json,--dry-run, reproducible--nowfor tests. - Zero dependencies, Python ≥ 3.9.
Install (pip)
pip install appendlog @ git+https://mandrilly.com/git/appendlog.git
Usage
# insert "- **🗓️ 22/09 01:30 — done thing**" after <!-- LOG --> in plan.md
appendlog plan.md "done thing"
# custom marker / template / stamp
appendlog state.md "check ran clean" --marker '<!-- AUDIT -->' \
--template '* [{stamp}] {text}' --stamp-format '%Y-%m-%d %H:%M'
appendlog plan.md "hello" --dry-run
appendlog plan.md "hello" --json
Python API: from appendlog.core import append_entry.
Exit codes
| Code | Meaning |
|---|---|
0 | inserted, duplicate (no-op), or dry-run |
1 | error (file missing, marker missing, empty text) |
2 | usage / invalid --now |
Tests
python -m unittest tests -v # 9 tests