docs: Change issue template to yml

[mors119]

Change issue templates filename extension.
md to yaml.

Summary by CodeRabbit

• Chores
  • Modernized GitHub issue templates from markdown to an improved structured format with enhanced validation and required input fields. Bug reports, feature requests, epics, and task templates now include dedicated sections for better organization. This ensures users provide more comprehensive information when submitting issues, improving visibility and tracking across the project.

[coderabbitai]

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 9d842fee-edcf-4abc-917c-abde72681ed5

📥 Commits

Reviewing files that changed from the base of the PR and between 871224a and 0b51ebc.

📒 Files selected for processing (10)

• .github/ISSUE_TEMPLATE/BUG_REPORT.md
• .github/ISSUE_TEMPLATE/EPIC.md
• .github/ISSUE_TEMPLATE/FEATURE_REQUEST.md
• .github/ISSUE_TEMPLATE/FEATURE_TESK.md
• .github/ISSUE_TEMPLATE/TASK.md
• .github/ISSUE_TEMPLATE/bug_report.yml
• .github/ISSUE_TEMPLATE/epic.yml
• .github/ISSUE_TEMPLATE/feature.yml
• .github/ISSUE_TEMPLATE/feature_request.yml
• .github/ISSUE_TEMPLATE/task.yml

---

📝 Walkthrough

Walkthrough

The PR migrates the repository's GitHub issue templates from legacy Markdown format to standardized YAML form templates, replacing five .md templates with corresponding .yml files that define structured fields, validations, labels, and title prefixes for bug reports, epics, features, feature requests, and tasks.

Changes

GitHub Issue Template Configuration

Layer / File(s)

Summary

GitHub issue form templates in YAML .github/ISSUE_TEMPLATE/bug_report.yml, .github/ISSUE_TEMPLATE/epic.yml, .github/ISSUE_TEMPLATE/feature.yml, .github/ISSUE_TEMPLATE/feature_request.yml, .github/ISSUE_TEMPLATE/task.yml

Five YAML issue form templates replace the legacy Markdown templates. Bug report template defines required fields for bug description, reproduction steps, expected/actual behavior, OS, Rust version, and environment details. Epic template requires goal and includes textarea fields with automatic epic label. Feature template includes description and tasks fields with [FEATURE] prefix and enhancement label. Feature request template adds description, expected behavior, optional notes, and a verification checklist. Task template defines description and done-when conditions with task label and checklist placeholders.

Estimated Code Review Effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly Related PRs

• FrilLab/dustfril#4: Related issue template configuration update that modifies the Markdown issue template definitions under .github/ISSUE_TEMPLATE/.

Poem

🐰 Templates in YAML, forms so clean and bright,
Old markdown templates fade into the night,
Five golden templates dance in perfect rows,
Bug reports, epics, features—oh how it flows!
The rabbit says: structured issues steal the show! ✨

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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