Skip to content

Add feature report issue template in YAML format#17

Merged
mors119 merged 1 commit into
mainfrom
mors119-patch-2
Jun 11, 2026
Merged

Add feature report issue template in YAML format#17
mors119 merged 1 commit into
mainfrom
mors119-patch-2

Conversation

@mors119

@mors119 mors119 commented Jun 11, 2026

Copy link
Copy Markdown
Collaborator

Summary

Add feature report issue template in YAML format

Type of Change

  • feat
  • fix
  • docs
  • refactor
  • test
  • chore

Summary by CodeRabbit

  • Chores
    • Updated feature request template format for improved usability and consistency.

@coderabbitai

coderabbitai Bot commented Jun 11, 2026

Copy link
Copy Markdown

Review Change Stack

Caution

Review failed

Pull request was closed or merged during review

📝 Walkthrough

Walkthrough

The PR replaces the markdown-based feature request issue template with GitHub's newer YAML-based issue form format. The new template defines required fields for Problem and Proposed Solution, plus optional fields for Alternatives and Additional Context, along with metadata and an enhancement label.

Changes

Issue Template Migration

Layer / File(s) Summary
Feature Request template form
.github/ISSUE_TEMPLATE/FEATURE_REPORT.yml
New GitHub issue form template replaces the markdown version, defining form metadata and four textarea fields (Problem and Proposed Solution required; Alternatives and Additional Context optional) with an enhancement label.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Poem

🐰 A template once worn, now shiny and new,
From markdown to YAML, a clean form review,
Feature requests flow with structured grace,
GitHub's new forms help developers embrace,
Change that improves without bother or fuss! ✨

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main change: removing the old markdown feature report template and adding a new YAML-formatted issue template.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ 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 mors119-patch-2

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

@mors119 mors119 merged commit 3d50ca4 into main Jun 11, 2026
1 of 2 checks passed
@mors119 mors119 deleted the mors119-patch-2 branch June 11, 2026 01:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant