e01b7412d9
Adds comprehensive Git worktree support for beads issue tracking: Core changes: - New internal/git/gitdir.go package for worktree detection - GetGitDir() returns proper .git location (main repo, not worktree) - Updated all hooks to use git.GetGitDir() instead of local helper - BeadsDir() now prioritizes main repository's .beads directory Features: - Hooks auto-install in main repo when run from worktree - Shared .beads directory across all worktrees - Config option no-install-hooks to disable auto-install - New bd worktree subcommand for diagnostics Documentation: - New docs/WORKTREES.md with setup instructions - Updated CHANGELOG.md and AGENT_INSTRUCTIONS.md Testing: - Updated tests to use exported git.GetGitDir() - Added worktree detection tests Co-authored-by: Claude <noreply@anthropic.com> Closes: #478
745 B
745 B
description, argument-hint
| description | argument-hint | |
|---|---|---|
| Initialize beads in the current project |
|
Initialize beads issue tracking in the current directory.
If a prefix is provided as $1, use it as the issue prefix (e.g., "myproject" creates issues like myproject-1, myproject-2). If not provided, the default is the current directory name.
Use the beads MCP init tool with the prefix parameter (if provided) to set up a new beads database.
After initialization:
- Show the database location
- Show the issue prefix that will be used
- Explain the basic workflow (or suggest running
/bd-workflow) - Suggest creating the first issue with
/bd-create
If beads is already initialized, inform the user and show project stats using the stats tool.