📝 docs: add GitHub issue templates

[AmintaCCCP]

Add Bug Report and New Feature issue form templates to standardize user reports and feature requests.

Summary by CodeRabbit

• Chores
  • Added standardized GitHub issue templates for bug reports and feature requests to streamline community contributions.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 9be702e6-1e56-4714-a09f-7122e15ba613

📥 Commits

Reviewing files that changed from the base of the PR and between c99514f and 420932b.

📒 Files selected for processing (2)

• .github/ISSUE_TEMPLATE/bug_report.yml
• .github/ISSUE_TEMPLATE/feature_request.yml

---

📝 Walkthrough

Walkthrough

Two GitHub issue templates are introduced to standardize bug report and feature request submissions. The bug report template captures platform, backend mode, reproduction steps, logs, and screenshots. The feature request template collects scenario descriptions, proposed solutions, and additional context. Both templates include markdown guidance and validation rules in Chinese.

Changes

GitHub Issue Templates

Layer / File(s)	Summary
Bug report template .github/ISSUE_TEMPLATE/bug_report.yml	Template defines bug submission form with required fields for title, platform, backend mode, and bug description (including expected behavior and reproduction steps), plus optional sections for logs, screenshots, and video attachments.
Feature request template .github/ISSUE_TEMPLATE/feature_request.yml	Template defines feature submission form with markdown intro and required/optional textarea fields for scenario description, proposed solution, and additional context, labeled with enhancement tag.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 Two templates now grace the repo's door,
Bug reports and features, organized with care,
Contributors flow through forms so fair,
No more confusion—just structure and flair!
GitHub issues bloom, both Chinese and bright.

🚥 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 reflects the main change: adding GitHub issue templates for bug reports and feature requests.
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 chore/add-issue-templates

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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