d06e3ea ("cleanup of noisey beads files", 2026-08-15) untracked
.beads/issues.jsonl on the rationale that JSONL exports are local
interchange artifacts. That reverses here: the export is now tracked so
issue state is readable and recoverable from a plain git clone, without
standing up a Dolt server.
What has NOT changed is which store is authoritative. Dolt still is, synced
via refs/dolt/data, with GitHub Issues as the external surface. The tracked
file is a mirror, not a source: it is written by bd's auto-export and must
never be hand-edited, because the next export overwrites it.
export.git-add flips to true in the same change, and the two settings only
make sense together. The exporter runs on a 60s interval and on the
pre-commit hook, so a tracked file that is not auto-staged would sit
permanently dirty in git status and block rebases and checkouts until
stashed -- the same friction .beads/interactions.jsonl already causes.
Staging it with the commit that regenerates it is what makes tracking
tolerable.
The cost accepted: most commits now carry issue churn, and parallel branches
can conflict on this file. Resolve such a conflict by taking either side and
re-running `bd export` -- the content is derived, so neither side is more
correct than the other.
Removing the ignore line is what tracks the file. Do not "fix" this with a
!issues.jsonl negation: .beads/.gitignore warns that negations override the
fork protection in .git/info/exclude.
90 lines
2.4 KiB
Plaintext
90 lines
2.4 KiB
Plaintext
# Dolt database (managed by Dolt, not git)
|
|
dolt/
|
|
embeddeddolt/
|
|
proxieddb/
|
|
|
|
# Runtime files
|
|
bd.sock
|
|
bd.sock.startlock
|
|
sync-state.json
|
|
last-touched
|
|
.exclusive-lock
|
|
|
|
# Daemon runtime (lock, log, pid)
|
|
daemon.*
|
|
|
|
# Push state (runtime, per-machine)
|
|
push-state.json
|
|
|
|
# Lock files (various runtime locks)
|
|
*.lock
|
|
|
|
# Credential key (encryption key for federation peer auth — never commit)
|
|
.beads-credential-key
|
|
|
|
# Local version tracking (prevents upgrade notification spam after git ops)
|
|
.local_version
|
|
|
|
proxied_server_client_info.json
|
|
|
|
# Worktree redirect file (contains relative path to main repo's .beads/)
|
|
# Must not be committed as paths would be wrong in other clones
|
|
redirect
|
|
|
|
# Sync state (local-only, per-machine)
|
|
# These files are machine-specific and should not be shared across clones
|
|
.sync.lock
|
|
|
|
# Workspace operation gate (internal/workspacegate): physical-root gate
|
|
# files live beside the guarded root inside .beads (e.g. dolt.gate.lock)
|
|
*.gate.lock*
|
|
export-state/
|
|
export-state.json
|
|
last_pull
|
|
|
|
# Ephemeral store (SQLite - wisps/molecules, intentionally not versioned)
|
|
ephemeral.sqlite3
|
|
ephemeral.sqlite3-journal
|
|
ephemeral.sqlite3-wal
|
|
ephemeral.sqlite3-shm
|
|
|
|
# Dolt server management (auto-started by bd)
|
|
dolt-server.pid
|
|
dolt-server.log
|
|
dolt-server.lock
|
|
dolt-server.port
|
|
dolt-server.activity
|
|
|
|
# Debug-mode pprof artifacts (written when dolt.debug: true in config.yaml)
|
|
dolt-pprof/
|
|
|
|
# Corrupt backup directories (created by bd doctor --fix recovery)
|
|
*.corrupt.backup/
|
|
|
|
# issues.jsonl is deliberately TRACKED (see export.git-add in config.yaml).
|
|
# Dolt remains the authoritative store and GitHub the external issue surface;
|
|
# the tracked export exists so issue state is readable and recoverable from a
|
|
# plain git clone, without a Dolt server. Removing it from this file is what
|
|
# tracks it -- do NOT add a "!issues.jsonl" negation, which would override the
|
|
# fork protection in .git/info/exclude (see the note at the end of this file).
|
|
#
|
|
# Backups stay local: they are point-in-time copies of the same data.
|
|
backup/
|
|
|
|
# Per-project environment file (Dolt connection config, GH#2520)
|
|
.env
|
|
|
|
# Legacy files (from pre-Dolt versions)
|
|
*.db
|
|
*.db?*
|
|
*.db-journal
|
|
*.db-wal
|
|
*.db-shm
|
|
db.sqlite
|
|
bd.db
|
|
# NOTE: Do NOT add negation patterns here.
|
|
# They would override fork protection in .git/info/exclude.
|
|
# Config files (metadata.json, config.yaml) are tracked by git by default
|
|
# since no pattern above ignores them.
|
|
# config.yaml
|