44 lines
1.2 KiB
YAML
44 lines
1.2 KiB
YAML
name: Feature request
|
|
description: A new feature, refactor, or design proposal for PureYAML.
|
|
labels: ["enhancement"]
|
|
body:
|
|
- type: input
|
|
id: status-date
|
|
attributes:
|
|
label: Status date
|
|
description: Today's date, in YYYY-MM-DD form. Keep this current as the issue evolves.
|
|
placeholder: 2026-05-29
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
id: goal
|
|
attributes:
|
|
label: Goal
|
|
description: What should be possible that is not possible today, and why does it matter?
|
|
validations:
|
|
required: true
|
|
- type: textarea
|
|
id: proposal
|
|
attributes:
|
|
label: Proposal
|
|
description: How might this work? Sketch the YAML, API, config, or workflow if you have one.
|
|
validations:
|
|
required: false
|
|
- type: textarea
|
|
id: acceptance
|
|
attributes:
|
|
label: Acceptance criteria
|
|
description: How will we know this is done?
|
|
validations:
|
|
required: true
|
|
- type: dropdown
|
|
id: priority
|
|
attributes:
|
|
label: Priority
|
|
description: High means release-gating or actively blocking other work. Otherwise leave as Normal.
|
|
options:
|
|
- Normal
|
|
- High
|
|
validations:
|
|
required: true
|