kimi-code/.github/ISSUE_TEMPLATE/2-feature-request.yml
qer 0f74525695
docs: enhance PR guidelines and template (#28)
* docs: enhance PR guidelines and template

* docs: refine contribution guidelines and issue templates

Clarify when to open an issue first, what can go straight to a PR,
and align CONTRIBUTING with the PR template without duplicating checklists.

Co-authored-by: Cursor <cursoragent@cursor.com>

* chore: update doc

---------

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-05-25 20:04:23 +08:00

26 lines
1,022 B
YAML

name: Feature Request
description: Propose a new feature for Kimi Code
labels:
- enhancement
body:
- type: markdown
attributes:
value: |
Is Kimi Code missing a feature that you'd like to see? Feel free to propose it here.
Before you submit a feature:
1. Search existing issues for similar features. If you find one, 👍 it rather than opening a new one.
2. The Kimi Code team will try to balance the varying needs of the community when prioritizing or rejecting new features. Please understand that not all features will be accepted.
3. Do not open a feature PR until maintainers have had a chance to respond here. PRs without prior discussion may be closed without review.
- type: textarea
id: feature
attributes:
label: What feature would you like to see?
validations:
required: true
- type: textarea
id: notes
attributes:
label: Additional information
description: Is there anything else you think we should know?