dd8c7595ba
Root cause: metadata.json is tracked in git and contains last_bd_version. When git operations (pull, checkout, merge) reset metadata.json to the committed version, the upgrade notification would fire repeatedly. Fix: Store the last used bd version in .beads/.local_version which is gitignored, so git operations don't affect version tracking. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <noreply@anthropic.com>
34 lines
607 B
Plaintext
34 lines
607 B
Plaintext
# SQLite databases
|
|
*.db
|
|
*.db?*
|
|
*.db-journal
|
|
*.db-wal
|
|
*.db-shm
|
|
|
|
# Daemon runtime files
|
|
daemon.lock
|
|
daemon.log
|
|
daemon.pid
|
|
bd.sock
|
|
|
|
# Local version tracking (prevents upgrade notification spam after git operations)
|
|
# bd-tok: Store version locally instead of in tracked metadata.json
|
|
.local_version
|
|
|
|
# Legacy database files
|
|
db.sqlite
|
|
bd.db
|
|
|
|
# Merge artifacts (temporary files from 3-way merge)
|
|
beads.base.jsonl
|
|
beads.base.meta.json
|
|
beads.left.jsonl
|
|
beads.left.meta.json
|
|
beads.right.jsonl
|
|
beads.right.meta.json
|
|
|
|
# Keep JSONL exports and config (source of truth for git)
|
|
!issues.jsonl
|
|
!metadata.json
|
|
!config.json
|