chore(meta): Updated bug/feature issue templates with types

[rllyy97]

Commit Type

• chore - Maintenance/tooling

Risk Level

• Low - Minor changes, limited scope
• Medium - Moderate changes, some user impact
• High - Major changes, significant user/system impact

What & Why

Updated bug/feature issue templates with types

Impact of Change

• Users: N/A
• Developers: Github issue templates will now be created with proper types
• System: N/A

Test Plan

• Unit tests added/updated
• E2E tests added/updated
• Manual testing completed
• Tested in:

Contributors

@rllyy97

Screenshots/Videos

N/A

[github-actions]

🤖 AI PR Validation Report

PR Review Results

Thank you for your submission! Here's detailed feedback on your PR title and body compliance:

✅ PR Title

• Current: chore(meta): Updated bug/feature issue templates with types
• Issue: Title is clear, follows conventional format, and includes scope and type.
• Recommendation: No changes needed; great job specifying change context and type.

---

✅ Commit Type

• Properly selected (chore - Maintenance/tooling)
• Only one selected, which is correct.

---

✅ Risk Level

• Risk level is selected as Low and matches label "Risk:Low". Assessment fits the scope (maintenance of issue templates only).

---

✅ What & Why

• Current: Updated bug/feature issue templates with types
• Issue: Brief and directly related to the content, though you could add a little detail if desired.
• Recommendation: Optional improvement: e.g. "Added type dropdowns to help triage issues faster."

---

✅ Impact of Change

• No user/system impact, small developer impact noted (better github triage). Matches the scope.
• Recommendation:
  • Users: N/A
  • Developers: Clearer issue categorization
  • System: N/A

---

✅ Test Plan

• None checked. This is acceptable for metadata/template changes without runtime code impact.

---

⚠️ Contributors

• Only self-tagged. Consider crediting any PMs, QA, or designers who contributed ideas if applicable. Not required.

---

✅ Screenshots/Videos

• Marked N/A, which is acceptable since these are template metadata files.

---

Summary Table

Section	Status	Recommendation
Title	✅	—
Commit Type	✅	—
Risk Level	✅	—
What & Why	✅	Optionally add a bit more context
Impact of Change	✅	—
Test Plan	✅	—
Contributors	⚠️	Credit others if applicable (optional)
Screenshots/Videos	✅	—

---

Everything required has been completed! This PR passes review for title and body compliance. No risk adjustment is needed. If others contributed, consider tagging them for credit. Thank you for helping maintain documentation quality!

---

Last updated: Thu, 04 Dec 2025 16:32:51 GMT

[Copilot]

Pull request overview

This PR attempts to add type classification to GitHub issue templates by introducing a type field to both bug and feature request templates. However, this introduces a configuration issue as the type field is not part of GitHub's official issue form schema.

Key Changes:

• Added type: 'Feature' field to feature_request.yml
• Added type: 'Bug' field to bug_report.yml
• Removed 'bug' label from bug_report.yml labels array

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File	Description
.github/ISSUE_TEMPLATE/feature_request.yml	Adds invalid type: 'Feature' field to template metadata
.github/ISSUE_TEMPLATE/bug_report.yml	Adds invalid type: 'Bug' field and removes 'bug' label from labels array

[Copilot]

The type field is not a valid top-level field in GitHub issue form templates. According to GitHub's issue form schema documentation, the valid top-level fields are: name, description, title, labels, assignees, and body. This field should be removed as it will either be ignored or cause the template to fail validation.

Suggested change

type: 'Bug'

[Copilot]

The 'bug' label was removed from the labels array. If this removal is intentional (to rely on the type field instead), please note that the type field is not valid and should be removed. The 'bug' label should likely be restored to maintain proper issue categorization, similar to how 'enhancement' is used in the feature_request.yml template.

Suggested change

	labels: ['triage']
	type: 'Bug'
	labels: ['triage', 'bug']

[Copilot]

The type field is not a valid top-level field in GitHub issue form templates. According to GitHub's issue form schema documentation, the valid top-level fields are: name, description, title, labels, assignees, and body. This field should be removed as it will either be ignored or cause the template to fail validation.

Suggested change

type: 'Feature'