refactor: Remove YAML template system entirely
Removes the legacy YAML-based simple template system that provided bug/epic/feature templates for --from-template flag on bd create. Removed: - cmd/bd/templates/bug.yaml, epic.yaml, feature.yaml - Template struct and all YAML loading functions in template.go - --from-template flag from bd create command - template_security_test.go (tested removed functions) - YAML template tests from template_test.go The Beads template system remains (epics with "template" label, instantiated via bd template instantiate with variable substitution). 🤖 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
@@ -1,56 +0,0 @@
|
||||
# Built-in template for bug reports
|
||||
name: bug
|
||||
description: |
|
||||
## Summary
|
||||
|
||||
[Brief description of the bug]
|
||||
|
||||
## Steps to Reproduce
|
||||
|
||||
1. Step 1
|
||||
2. Step 2
|
||||
3. Step 3
|
||||
|
||||
## Expected Behavior
|
||||
|
||||
[What should happen]
|
||||
|
||||
## Actual Behavior
|
||||
|
||||
[What actually happens]
|
||||
|
||||
## Environment
|
||||
|
||||
- OS: [e.g., macOS 15.7.1]
|
||||
- Version: [e.g., bd 0.20.1]
|
||||
- Additional context: [any relevant details]
|
||||
|
||||
## Additional Context
|
||||
|
||||
[Screenshots, logs, or other relevant information]
|
||||
|
||||
type: bug
|
||||
priority: 1
|
||||
labels:
|
||||
- bug
|
||||
|
||||
design: |
|
||||
## Root Cause Analysis
|
||||
|
||||
[Describe the underlying cause once identified]
|
||||
|
||||
## Proposed Fix
|
||||
|
||||
[Outline the solution approach]
|
||||
|
||||
## Impact Assessment
|
||||
|
||||
- Affected features: [list]
|
||||
- Breaking changes: [yes/no and details]
|
||||
- Migration needed: [yes/no and details]
|
||||
|
||||
acceptance_criteria: |
|
||||
- [ ] Bug no longer reproduces with original steps
|
||||
- [ ] Regression tests added
|
||||
- [ ] Related edge cases tested
|
||||
- [ ] Documentation updated if behavior changed
|
||||
@@ -1,51 +0,0 @@
|
||||
# Built-in template for creating epics
|
||||
name: epic
|
||||
description: |
|
||||
## Overview
|
||||
|
||||
[Describe the high-level goal and scope of this epic]
|
||||
|
||||
## Success Criteria
|
||||
|
||||
- [ ] Criteria 1
|
||||
- [ ] Criteria 2
|
||||
- [ ] Criteria 3
|
||||
|
||||
## Background
|
||||
|
||||
[Provide context and motivation]
|
||||
|
||||
## Scope
|
||||
|
||||
**In Scope:**
|
||||
- Item 1
|
||||
- Item 2
|
||||
|
||||
**Out of Scope:**
|
||||
- Item 1
|
||||
- Item 2
|
||||
|
||||
type: epic
|
||||
priority: 1
|
||||
labels:
|
||||
- epic
|
||||
|
||||
design: |
|
||||
## Architecture
|
||||
|
||||
[Describe the overall architecture and approach]
|
||||
|
||||
## Components
|
||||
|
||||
- Component 1: [description]
|
||||
- Component 2: [description]
|
||||
|
||||
## Dependencies
|
||||
|
||||
[List external dependencies or constraints]
|
||||
|
||||
acceptance_criteria: |
|
||||
- [ ] All child issues are completed
|
||||
- [ ] Integration tests pass
|
||||
- [ ] Documentation is updated
|
||||
- [ ] Code review completed
|
||||
@@ -1,60 +0,0 @@
|
||||
# Built-in template for feature requests
|
||||
name: feature
|
||||
description: |
|
||||
## Feature Request
|
||||
|
||||
[Describe the desired feature]
|
||||
|
||||
## Motivation
|
||||
|
||||
[Why is this feature needed? What problem does it solve?]
|
||||
|
||||
## Use Cases
|
||||
|
||||
1. **Use Case 1**: [description]
|
||||
2. **Use Case 2**: [description]
|
||||
|
||||
## Proposed Solution
|
||||
|
||||
[High-level approach to implementing this feature]
|
||||
|
||||
## Alternatives Considered
|
||||
|
||||
- **Alternative 1**: [description and why not chosen]
|
||||
- **Alternative 2**: [description and why not chosen]
|
||||
|
||||
type: feature
|
||||
priority: 2
|
||||
labels:
|
||||
- feature
|
||||
|
||||
design: |
|
||||
## Technical Design
|
||||
|
||||
[Detailed technical approach]
|
||||
|
||||
## API Changes
|
||||
|
||||
[New commands, flags, or APIs]
|
||||
|
||||
## Data Model Changes
|
||||
|
||||
[Database schema changes if any]
|
||||
|
||||
## Implementation Notes
|
||||
|
||||
- Note 1
|
||||
- Note 2
|
||||
|
||||
## Testing Strategy
|
||||
|
||||
- Unit tests: [scope]
|
||||
- Integration tests: [scope]
|
||||
- Manual testing: [steps]
|
||||
|
||||
acceptance_criteria: |
|
||||
- [ ] Feature implements all described use cases
|
||||
- [ ] All tests pass
|
||||
- [ ] Documentation updated (README, commands)
|
||||
- [ ] Examples added if applicable
|
||||
- [ ] No performance regressions
|
||||
Reference in New Issue
Block a user