PureYAML/.github/ISSUE_TEMPLATE/feature_request.yml
Mihaela M 9acfd57acc chore(issues): add required complexity field and a form labeler
Add the Complexity dropdown that Rule 1.6 requires on both issue forms
(status date, priority, complexity), alongside the existing per-kind
fields. Add a labeler workflow that maps the Priority dropdown to the
priority: high label on issue open and edit, closing the Rule 1.6
gotcha where form dropdowns produce body text but never apply a label.
Complexity stays a body field only, never a label, per Rule 2.1.
2026-06-26 05:48:01 +02:00

55 lines
1.5 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
- type: dropdown
id: complexity
attributes:
label: Complexity
description: A rough effort estimate. Small is a focused change; Large spans many files or needs design.
options:
- Small
- Medium
- Large
validations:
required: true