Create feature_request.yml

[wscurran]

v1 feature request template that auto applies label "status: triage"

Summary by CodeRabbit

• Chores
  • Added a standardized GitHub issue template for feature and enhancement requests to streamline proposal submissions and ensure structured feedback collection.

[coderabbitai]

📝 Walkthrough

Walkthrough

A new GitHub issue template is added to standardize feature and enhancement requests. The template includes a structured form with required fields for proposed changes and categorization options, with automatic triage labeling upon submission.

Changes

Cohort / File(s)	Summary
GitHub Issue Template .github/ISSUE_TEMPLATE/feature_request.yml	New feature request template with structured form fields: required textarea for proposed changes and required dropdown for categorization (feature, provider, platform, testing). Automatically applies "status: triage" label.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 A template springs forth from the config,
With fields so clear, oh what a topic!
Features and dreams now have a home,
Structured requests shall freely roam!
Hop-hop-hooray for triage's gleam! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'Create feature_request.yml' is fully related to the main change in the changeset. It directly and clearly summarizes the primary objective: adding a new GitHub issue template file.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch wscurran-triage-templates-1

📝 Coding Plan

• Generate coding plan for human review comments

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/issue-templates/feature_request.yml:
- Around line 1-2: The issue is that the issue template file
(feature_request.yml) is in the wrong folder and lacks a description field; move
the template file to the repository's recognized ISSUE_TEMPLATE location and add
a top-level description key to the YAML (alongside the existing name and labels
keys) explaining the template's purpose so GitHub will surface it in the issue
picker.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 018d6cef-70ee-4302-ab3c-e5d9bc68752d

📥 Commits

Reviewing files that changed from the base of the PR and between 88a7c40 and 38ebc8b.

📒 Files selected for processing (1)

• .github/issue-templates/feature_request.yml

[wscurran]

Updated incorrect folder name for templates.

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/ISSUE_TEMPLATE/feature_request.yml:
- Line 2: The YAML key is malformed and the grammar is wrong: change the
top-level key from "+description" to "description" and update its value string
to read "Submit a feature request or enhancement to help us improve NemoClaw"
(replace "request other enhancement" with "request or enhancement") so the
GitHub issue form uses a valid key and correct wording.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: b098cfff-22de-4248-8453-2a00936f417b

📥 Commits

Reviewing files that changed from the base of the PR and between 38ebc8b and 3fdee70.

📒 Files selected for processing (1)

• .github/ISSUE_TEMPLATE/feature_request.yml

[coderabbitai]

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🌐 Web query:

GitHub issue forms YAML: what are the valid top-level keys, and should the metadata field be description(not+description)?

💡 Result:

Valid top-level keys in a GitHub issue form YAML are: name, description, body (all required), plus optional assignees, labels, title, type, projects. [1]

So the metadata field is description (no plus sign). A key like +description is not part of the supported schema and will be treated as an unexpected/unpermitted top-level key. [1][2]

---

Fix the malformed key and grammar on Line 2.

+description is not a valid top-level key in GitHub issue forms; it should be description. Additionally, the text should read "feature request or enhancement" instead of "request other enhancement".

Suggested fix

-+description: Submit a feature request other enhancement to help us improve NemoClaw
+description: Submit a feature request or enhancement to help us improve NemoClaw

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	+description: Submit a feature request other enhancement to help us improve NemoClaw
	description: Submit a feature request or enhancement to help us improve NemoClaw

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.github/ISSUE_TEMPLATE/feature_request.yml at line 2, The YAML key is
malformed and the grammar is wrong: change the top-level key from "+description"
to "description" and update its value string to read "Submit a feature request
or enhancement to help us improve NemoClaw" (replace "request other enhancement"
with "request or enhancement") so the GitHub issue form uses a valid key and
correct wording.