7d35ced5ae
Allow changing an issue type (bug, feature, task, epic, chore) via the bd update command. The storage layer already supported issue_type in allowedUpdateFields, this just exposes it through the CLI. Changes: - Add --type/-t flag to updateCmd in show.go - Add IssueType field to UpdateArgs in protocol.go - Handle issue_type in updatesFromArgs in server_issues_epics.go - Add validation using ParseIssueType before update Example usage: bd update ab-xyz --type epic Fixes: #522
35 lines
573 B
Plaintext
35 lines
573 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 ops)
|
|
.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
|
|
deletions.jsonl
|
|
deletions.jsonl.migrated
|