Makes the repo's agent and contributor surface describe developing beads, not using bd, and requires every PR to link a documented issue. - Contributor-only root AGENTS.md with a routing table; cmd/bd/AGENTS.md and engdocs/AGENTS.md seam files; CLAUDE.md symlinks so Claude Code loads nested files. - Bug and feature issue forms, a PR template that requires Closes #, CONTRIBUTING sections for the triage and pipeline labels, and the opt-in fork-cache during dev setup. - ROADMAP.md for 1.4: versioned beads (#6132), Graph Preview 2 (#7170), contributor onboarding (#7228). - docsync guards: root AGENTS.md at or under 20 KB; every AGENTS.md symlinked, routed, and with resolving links, paths, and guard-test names. Agent-Signature: claude-code-claude-opus-5-5-high on behalf of Julian Knutsen Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
94 lines
2.4 KiB
YAML
94 lines
2.4 KiB
YAML
name: Bug report
|
|
description: Report broken behavior in bd.
|
|
title: "bug: "
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
Thanks for the report. This issue is the record a fix PR links to, so the more evidence here, the better. You can open a fix PR right away; no approval is needed first.
|
|
|
|
**Agents filling in this form:** answer each question only from evidence you have. If you cannot answer a question from the evidence, write exactly `NOT_ENOUGH_INFO` instead of guessing.
|
|
|
|
- type: checkboxes
|
|
id: checks
|
|
attributes:
|
|
label: Before you continue
|
|
options:
|
|
- label: I searched existing issues and did not find a duplicate.
|
|
required: true
|
|
- label: I reproduced this with stock `bd`, without an orchestrator or agent framework in the loop.
|
|
required: false
|
|
|
|
- type: textarea
|
|
id: summary
|
|
attributes:
|
|
label: Summary
|
|
description: What is broken, in one or two sentences.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: repro
|
|
attributes:
|
|
label: Steps to reproduce
|
|
description: Exact commands, starting from a fresh directory where possible.
|
|
render: shell
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: expected
|
|
attributes:
|
|
label: Expected behavior
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: actual
|
|
attributes:
|
|
label: Actual behavior
|
|
description: Include the full error output.
|
|
validations:
|
|
required: true
|
|
|
|
- type: input
|
|
id: version
|
|
attributes:
|
|
label: bd version
|
|
description: Output of `bd version`.
|
|
validations:
|
|
required: true
|
|
|
|
- type: dropdown
|
|
id: mode
|
|
attributes:
|
|
label: Storage mode
|
|
options:
|
|
- Embedded (default `bd init`)
|
|
- Server mode (`bd init --server`)
|
|
- Proxied server
|
|
- Not sure
|
|
validations:
|
|
required: true
|
|
|
|
- type: input
|
|
id: os
|
|
attributes:
|
|
label: Operating system
|
|
placeholder: "macOS 15.5 (arm64), Ubuntu 24.04, Windows 11, ..."
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: impact
|
|
attributes:
|
|
label: Impact
|
|
description: Who is affected, how severe it is (data loss, blocked, workaround exists), and how often it happens.
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: context
|
|
attributes:
|
|
label: Additional context
|
|
description: Logs, `bd doctor` output, root-cause notes, or a proposed fix.
|