- Updated FAQ.md, ADVANCED.md, TROUBLESHOOTING.md to explain hash IDs eliminate collisions - Removed --resolve-collisions references from all documentation and examples - Renamed handleCollisions() to detectUpdates() to reflect update semantics - Updated test names: TestAutoImportWithCollision → TestAutoImportWithUpdate - Clarified: with hash IDs, same-ID = update operation, not collision Closes: bd-50a7, bd-b84f, bd-bda8, bd-650c, bd-3ef2, bd-c083, bd-85a6
989 B
989 B
description, argument-hint
| description | argument-hint | |
|---|---|---|
| Import issues from JSONL format |
|
Import issues from JSON Lines format (one JSON object per line).
Usage
- From stdin:
bd import(reads from stdin) - From file:
bd import -i issues.jsonl - Preview:
bd import -i issues.jsonl --dry-run
Behavior
- Existing issues (same ID): Updated with new data
- New issues: Created
- Same-ID scenarios: With hash-based IDs (v0.20.1+), same ID = same issue being updated (not a collision)
Preview Changes
Use --dry-run to see what will change before importing:
bd import -i issues.jsonl --dry-run
# Shows: new issues, updates, exact matches
Automatic Import
The daemon automatically imports from .beads/issues.jsonl when it's newer than the database (e.g., after git pull). Manual import is rarely needed.
Options
- --skip-existing: Skip updates to existing issues
- --strict: Fail on dependency errors instead of warnings