* feat(docs): version Docusaurus site and align llms-full with snapshots Add docs version 1.0.0, version dropdown, lastVersion defaulting to stable, merged markdown config, and RELEASING steps for future doc snapshots. generate-llms-full.sh reads the latest entry in versions.json. README links the published documentation site. Closes #2644 Made-with: Cursor * fix(docs): update org URLs to gastownhall and refresh 1.0.0 snapshot - Update default orgName in docusaurus.config.ts from steveyegge to gastownhall to match the repo's new home - Update hardcoded steveyegge URLs in generate-llms-full.sh - Refresh versioned_docs 1.0.0 snapshot to include quickstart changes from #3032 which merged after the original snapshot was taken - Regenerate llms-full.txt with corrected URLs and updated content Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: matt wilkie <maphew@gmail.com> Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2.3 KiB
2.3 KiB
| id | title | sidebar_position |
|---|---|---|
| labels | Labels & Comments | 5 |
Labels & Comments
Commands for managing labels and comments.
Labels
Adding Labels
# During creation
bd create "Task" -l "backend,urgent"
# To existing issue
bd update bd-42 --add-label urgent
bd update bd-42 --add-label "backend,security"
Removing Labels
bd update bd-42 --remove-label urgent
Listing Labels
# All labels in use
bd label list
bd label list --json
# Issues with specific labels
bd list --label-any urgent,critical
bd list --label-all backend,security
Label Conventions
Suggested label categories:
| Category | Examples | Purpose |
|---|---|---|
| Type | bug, feature, docs |
Issue classification |
| Priority | urgent, critical |
Urgency markers |
| Area | backend, frontend, api |
Code area |
| Status | blocked, needs-review |
Workflow state |
| Size | small, medium, large |
Effort estimate |
Comments
Adding Comments
bd comment add bd-42 "Working on this now"
bd comment add bd-42 --message "Found the bug in auth.go:45"
Listing Comments
bd comment list bd-42
bd comment list bd-42 --json
Viewing with Issue
bd show bd-42 --full # Includes comments
Filtering by Labels
Any Match (OR)
# Issues with urgent OR critical
bd list --label-any urgent,critical
All Match (AND)
# Issues with BOTH backend AND security
bd list --label-all backend,security
Combined Filters
# Open bugs with urgent label
bd list --status open --type bug --label-any urgent --json
Bulk Operations
Add Label to Multiple Issues
# Using shell
for id in bd-42 bd-43 bd-44; do
bd update $id --add-label "sprint-1"
done
Find and Label
# Label all open bugs as needs-triage
bd list --status open --type bug --json | \
jq -r '.[].id' | \
xargs -I {} bd update {} --add-label needs-triage
Best Practices
- Keep labels lowercase -
backendnotBackend - Use hyphens for multi-word -
needs-reviewnotneeds_review - Be consistent - Establish team conventions
- Don't over-label - 2-4 labels per issue is typical
- Review periodically - Remove unused labels