qmd/.beads
Tobi Lutke 5f68faa853
Migrate documents table to use collection names instead of IDs
Schema changes:
- documents.collection_id (INTEGER FK) → documents.collection (TEXT)
- Update UNIQUE constraint to (collection, path)
- Update indices to use collection name
- Update FTS triggers to compute filepath from collection || '/' || path

Code changes in store.ts:
- Change all function parameters from collectionId: number to collectionName: string
- Update all SQL queries to use d.collection instead of d.collection_id
- Remove unnecessary JOINs where collection name is already available
- Update DocumentResult type: collectionId → collectionName
- Update renameCollection() to also update documents.collection

Successfully migrated 2309 documents across 6 collections.

This prepares for YAML-based collection configuration where collections
table will be removed and collection names will be the primary identifier.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2025-12-13 10:08:24 -05:00
..
.gitignore Update get and multi-get commands for virtual paths 2025-12-12 15:47:42 -05:00
.local_version Update get and multi-get commands for virtual paths 2025-12-12 15:47:42 -05:00
config.yaml Update get and multi-get commands for virtual paths 2025-12-12 15:47:42 -05:00
issues.jsonl Migrate documents table to use collection names instead of IDs 2025-12-13 10:08:24 -05:00
metadata.json bd sync: 2025-12-12 15:31:28 2025-12-12 15:31:28 -05:00
README.md Update get and multi-get commands for virtual paths 2025-12-12 15:47:42 -05:00

Beads - AI-Native Issue Tracking

Welcome to Beads! This repository uses Beads for issue tracking - a modern, AI-native tool designed to live directly in your codebase alongside your code.

What is Beads?

Beads is issue tracking that lives in your repo, making it perfect for AI coding agents and developers who want their issues close to their code. No web UI required - everything works through the CLI and integrates seamlessly with git.

Learn more: github.com/steveyegge/beads

Quick Start

Essential Commands

# Create new issues
bd create "Add user authentication"

# View all issues
bd list

# View issue details
bd show <issue-id>

# Update issue status
bd update <issue-id> --status in_progress
bd update <issue-id> --status done

# Sync with git remote
bd sync

Working with Issues

Issues in Beads are:

  • Git-native: Stored in .beads/issues.jsonl and synced like code
  • AI-friendly: CLI-first design works perfectly with AI coding agents
  • Branch-aware: Issues can follow your branch workflow
  • Always in sync: Auto-syncs with your commits

Why Beads?

AI-Native Design

  • Built specifically for AI-assisted development workflows
  • CLI-first interface works seamlessly with AI coding agents
  • No context switching to web UIs

🚀 Developer Focused

  • Issues live in your repo, right next to your code
  • Works offline, syncs when you push
  • Fast, lightweight, and stays out of your way

🔧 Git Integration

  • Automatic sync with git commits
  • Branch-aware issue tracking
  • Intelligent JSONL merge resolution

Get Started with Beads

Try Beads in your own projects:

# Install Beads
curl -sSL https://raw.githubusercontent.com/steveyegge/beads/main/scripts/install.sh | bash

# Initialize in your repo
bd init

# Create your first issue
bd create "Try out Beads"

Learn More


Beads: Issue tracking that moves at the speed of thought