feat: add events JSONL export (opt-in via events.export config) #1305
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add GetAllEventsSince to the Storage interface and implement it in
SQLite, Dolt, and Memory backends. Create exportEventsToJSONL which
reads events_last_exported_id from metadata, fetches new events, appends
them as JSON lines, and updates the high-water mark.
Hook the events export into daemon_sync and autoflush, guarded by
config.GetBool("events.export") so it's opt-in. Add events.jsonl to
the sync file list in gitCommitBeadsDir. Add --events and --events-reset
flags to the export command (always available regardless of config).
Include a test verifying GetAllEventsSince returns all event columns.
Tickets: bd-w9f, bd-8fq, bd-w9w, bd-1ai, bd-2qd, bd-b22, bd-mmc, bd-3pc
The events.jsonl file uses 0644 permissions (matching issues.jsonl) since it needs to be readable by other tools and git. Ticket: bd-gdw
Satisfies gosec G302 lint check. Git normalizes permissions on checkout anyway, so this only affects the local write. Ticket: bd-gdw
Add commented-out example for the events.export option in both the init template (for new projects) and the repo config.yaml.
Matches the doc comment style used in SQLite and Dolt implementations.
Viper uses "." as a nested key delimiter, so "events.export" would
look for nested YAML (events: { export: true }) instead of the flat
key. Use hyphenated "events-export" to match existing conventions
(no-auto-flush, no-auto-import, etc.).
Also registers the default in config.go.
Ticket: bd-v2x
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
GetAllEventsSince(ctx, sinceID)to the Storage interface with SQLite, Dolt, and Memory implementationsexportEventsToJSONLwhich appends new events as JSON lines using a high-water mark (events_last_exported_idmetadata)events.exportconfig key (opt-in)events.jsonlto git sync file list--eventsand--events-resetflags tobd exportcommandConfiguration
Enable with
events.export: truein.beads/config.yaml. Thebd export --eventsflag works regardless of config.Test plan
go build ./...passesgo test ./internal/storage/...passes (all backends)TestGetAllEventsSinceReturnsAllColumnsverifies all columns are returnedevents.export: true, create/update issues, verify events.jsonl is populatedbd export --eventsworks without config setbd export --events-resetclears state and truncates fileTickets: bd-w9f, bd-8fq, bd-w9w, bd-1ai, bd-2qd, bd-b22, bd-mmc, bd-3pc
🤖 Generated with Claude Code