69 lines
1.8 KiB
YAML
69 lines
1.8 KiB
YAML
name: Feature request
|
|
description: Propose a product, workflow, integration, or engineering improvement.
|
|
title: "[Feature]: "
|
|
labels: ["enhancement", "needs-triage"]
|
|
body:
|
|
- type: markdown
|
|
attributes:
|
|
value: |
|
|
Please keep proposals focused and avoid sharing private customer data, prompts, screenshots with secrets, or provider credentials.
|
|
|
|
- type: textarea
|
|
id: problem
|
|
attributes:
|
|
label: Problem or opportunity
|
|
description: What user, operator, or developer problem does this solve?
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: proposal
|
|
attributes:
|
|
label: Proposed solution
|
|
description: Describe the behavior, API, UI, or documentation change.
|
|
validations:
|
|
required: true
|
|
|
|
- type: dropdown
|
|
id: area
|
|
attributes:
|
|
label: Area
|
|
options:
|
|
- Lovart home
|
|
- Canvas / Agent
|
|
- Image or video generation
|
|
- 3D / CAD
|
|
- Settings / admin
|
|
- API / backend
|
|
- Performance
|
|
- Security / observability
|
|
- Documentation / CI
|
|
- Other
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: alternatives
|
|
attributes:
|
|
label: Alternatives considered
|
|
description: What other approaches did you consider?
|
|
|
|
- type: textarea
|
|
id: acceptance
|
|
attributes:
|
|
label: Acceptance criteria
|
|
description: How should reviewers verify that this is done?
|
|
placeholder: |
|
|
- ...
|
|
- ...
|
|
|
|
- type: checkboxes
|
|
id: checks
|
|
attributes:
|
|
label: Pre-submit checklist
|
|
options:
|
|
- label: This request does not include real secrets, private prompts, signed URLs, or private user data.
|
|
required: true
|
|
- label: I checked the README, release readiness notes, and existing issues first.
|
|
required: true
|