beads/website/versioned_docs/version-1.0.0/cli-reference/labels.md
Isaac Karrer 7f0a165f4e
feat(docs): version Docusaurus site and align llms-full with snapshots (#3033)
* 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>
2026-04-06 21:12:54 -07:00

125 lines
2.3 KiB
Markdown

---
id: labels
title: Labels & Comments
sidebar_position: 5
---
# Labels & Comments
Commands for managing labels and comments.
## Labels
### Adding Labels
```bash
# 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
```bash
bd update bd-42 --remove-label urgent
```
### Listing Labels
```bash
# 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
```bash
bd comment add bd-42 "Working on this now"
bd comment add bd-42 --message "Found the bug in auth.go:45"
```
### Listing Comments
```bash
bd comment list bd-42
bd comment list bd-42 --json
```
### Viewing with Issue
```bash
bd show bd-42 --full # Includes comments
```
## Filtering by Labels
### Any Match (OR)
```bash
# Issues with urgent OR critical
bd list --label-any urgent,critical
```
### All Match (AND)
```bash
# Issues with BOTH backend AND security
bd list --label-all backend,security
```
### Combined Filters
```bash
# Open bugs with urgent label
bd list --status open --type bug --label-any urgent --json
```
## Bulk Operations
### Add Label to Multiple Issues
```bash
# Using shell
for id in bd-42 bd-43 bd-44; do
bd update $id --add-label "sprint-1"
done
```
### Find and Label
```bash
# 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
1. **Keep labels lowercase** - `backend` not `Backend`
2. **Use hyphens for multi-word** - `needs-review` not `needs_review`
3. **Be consistent** - Establish team conventions
4. **Don't over-label** - 2-4 labels per issue is typical
5. **Review periodically** - Remove unused labels