johno/beads
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(docs): use consistent in_progress status naming (GH#444)

Browse Source 
Changed all user-facing documentation and help text to use `in_progress`
(underscore) instead of `in-progress` (hyphen) to match the canonical
status value.

Files updated:
- cmd/bd/ready.go - Short description
- cmd/bd/status.go - Long description
- commands/stats.md - Action suggestion
- README.md - Workflow description

Note: CSS class names, HTML IDs, and GitHub label mappings intentionally
kept with hyphens as they follow different conventions.

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

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Steve Yegge
2025-12-16 01:07:33 -08:00
parent 8569259cf3
commit 4bf369a618
6 changed files with 218 additions and 212 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.beads/.gitignore vendored
View File

@@ -30,3 +30,5 @@ beads.right.meta.json
!issues.jsonl !issues.jsonl
!metadata.json !metadata.json
!config.json !config.json
deletions.jsonl
deletions.jsonl.migrated

420
.beads/issues.jsonl
View File

File diff suppressed because one or more lines are too long

2
README.md
View File

@@ -262,7 +262,7 @@ This pattern has proven invaluable for maintaining database hygiene and preventi
**1. File/update issues for remaining work** **1. File/update issues for remaining work**
- Agents should proactively create issues for discovered bugs, TODOs, and follow-up tasks - Agents should proactively create issues for discovered bugs, TODOs, and follow-up tasks
- Close completed issues and update status for in-progress work - Close completed issues and update status for in_progress work
**2. Run quality gates (if applicable)** **2. Run quality gates (if applicable)**
- Tests, linters, builds - only if code changes were made - Tests, linters, builds - only if code changes were made

2
cmd/bd/ready.go
View File

@@ -12,7 +12,7 @@ import (
) )
var readyCmd = &cobra.Command{ var readyCmd = &cobra.Command{
Use: "ready", Use: "ready",
Short: "Show ready work (no blockers, open or in-progress)", Short: "Show ready work (no blockers, open or in_progress)",
Run: func(cmd *cobra.Command, args []string) { Run: func(cmd *cobra.Command, args []string) {
limit, _ := cmd.Flags().GetInt("limit") limit, _ := cmd.Flags().GetInt("limit")
assignee, _ := cmd.Flags().GetString("assignee") assignee, _ := cmd.Flags().GetString("assignee")

2
cmd/bd/status.go
View File

@@ -45,7 +45,7 @@ var statusCmd = &cobra.Command{
Short: "Show issue database overview", Short: "Show issue database overview",
Long: `Show a quick snapshot of the issue database state. Long: `Show a quick snapshot of the issue database state.
This command provides a summary of issue counts by state (open, in-progress, This command provides a summary of issue counts by state (open, in_progress,
blocked, closed), ready work, and recent activity over the last 24 hours from git history. blocked, closed), ready work, and recent activity over the last 24 hours from git history.
Similar to how 'git status' shows working tree state, 'bd status' gives you Similar to how 'git status' shows working tree state, 'bd status' gives you

2
commands/stats.md
View File

@@ -13,5 +13,5 @@ Use the beads MCP `stats` tool to retrieve project metrics and present them clea
Optionally suggest actions based on the stats: Optionally suggest actions based on the stats:
- High number of blocked issues? Run `/bd-blocked` to investigate - High number of blocked issues? Run `/bd-blocked` to investigate
- No in-progress work? Run `/bd-ready` to find tasks - No in_progress work? Run `/bd-ready` to find tasks
- Many open issues? Consider prioritizing with `/bd-update` - Many open issues? Consider prioritizing with `/bd-update`