chore: add issue types and missing label to issue templates

[mootari]

🔗 Linked issue

Reference: https://discord.com/channels/1464542801676206113/1464544758020968448/1493981022411427861

🧭 Context

• New issues created from templates don't have a type assigned, requiring maintainers to add them manually.
• The bug template is missing the "pending triage" label.

📚 Description

Adds the type field to the bug and feature request template (see docs). The identifiers are case insensitive (see discussion).

Adds the label "pending triage" (currently only present in the feature request template) to the bug report template. Please note that the actual label had only been created earlier today, which is why (as of now) only one feature issue has the label assigned.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
npmx.dev	Ready	Preview, Comment	Apr 15, 2026 10:00pm

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ignored	Preview	Apr 15, 2026 10:00pm
npmx-lunaria	Ignored		Apr 15, 2026 10:00pm

[coderabbitai]

📝 Walkthrough

Walkthrough

Two GitHub issue template files were updated with metadata attributes. The bug-report template received type: bug and labels: ['pending triage'], whilst the feature-request template received type: feature. No template structure or validation logic was modified.

Changes

Cohort / File(s)	Summary
GitHub Issue Templates .github/ISSUE_TEMPLATE/bug-report.yml, .github/ISSUE_TEMPLATE/feature-request.yml	Added template type metadata: type: bug and labels: ['pending triage'] for bug reports; type: feature for feature requests.

Possibly related PRs

• chore: add issue/PR templates #1531: Modifies the same issue template files with overlapping metadata changes for type and labels attributes.

Suggested reviewers

• danielroe

🚥 Pre-merge checks | ✅ 2

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description is directly related to the changeset, explaining the context, motivation, and technical details of adding type fields and labels to issue templates.
Title check	✅ Passed	The title accurately summarizes the main changes: adding issue types and the 'pending triage' label to issue templates, which directly matches the modifications to bug-report.yml and feature-request.yml.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}

[github-actions]

Hello! Thank you for opening your first PR to npmx, @mootari! 🚀

Here’s what will happen next:

1. Our GitHub bots will run to check your changes.
   If they spot any issues you will see some error messages on this PR.
   Don’t hesitate to ask any questions if you’re not sure what these mean!

2. In a few minutes, you’ll be able to see a preview of your changes on Vercel

3. One or more of our maintainers will take a look and may ask you to make changes.
   We try to be responsive, but don’t worry if this takes a few days.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

[serhalp]

thank you!

[github-actions]

Thanks for your first contribution, @mootari! 🎊

We'd love to welcome you to the npmx community. Come and say hi on Discord! And once you've joined, visit npmx.wamellow.com to claim the contributor role.