Files
ccs/.github/ISSUE_TEMPLATE/feature-request.yml
T

65 lines
1.9 KiB
YAML

name: Feature request
description: Suggest a focused improvement for the CLI, dashboard, or contributor workflow.
title: "feat: "
labels:
- enhancement
body:
- type: markdown
attributes:
value: |
Feature requests land faster when they describe the user problem first and stay narrow.
Rough ideas are still welcome if they are grounded in a real workflow or pain point.
- type: dropdown
id: area
attributes:
label: Affected area
options:
- CLI runtime
- Dashboard UI
- Config or auth flow
- Provider integration
- Install or packaging
- Documentation
- Contributor workflow
- type: textarea
id: problem
attributes:
label: What problem are you trying to solve?
placeholder: I manage multiple profiles, but ...
validations:
required: true
- type: textarea
id: proposal
attributes:
label: Proposed solution or direction
placeholder: Add a command or dashboard control that ...
- type: textarea
id: user-flow
attributes:
label: Suggested user flow
description: Show the command, screen, or sequence you expect.
placeholder: |
CLI:
1. `ccs ...`
Dashboard:
1. Open ...
2. Click ...
- type: textarea
id: alternatives
attributes:
label: Alternatives considered
description: Existing workaround, rejected approach, or why current behavior is not enough.
- type: textarea
id: context
attributes:
label: Additional context
description: Mockups, screenshots, links to related issues, or compatibility notes.
- type: checkboxes
id: checks
attributes:
label: Before submitting
options:
- label: I searched existing issues and docs first.
- label: This request describes a concrete user problem, not just a broad idea dump.