chore: add issue templates for bug reports and pull + feature requests

[colinscz]

🔗 Linked issue

Resolves #1522

📚 Description

This PR introduces a minimal template for pull requests, bug reports and feature requests. It also offers a link to the Npmx docs upon clicking the "create issue" button. Credit goes mainly to what is already there on the Nuxt project.

Looks similar to this (minus discussion and security vulnerability options)

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
npmx.dev	Ready	Preview, Comment	Feb 16, 2026 1:39pm

2 Skipped Deployments

Project	Deployment	Actions	Updated (UTC)
docs.npmx.dev	Ignored	Preview	Feb 16, 2026 1:39pm
npmx-lunaria	Ignored		Feb 16, 2026 1:39pm

[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!

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

---

📝 Walkthrough

Walkthrough

Adds standardized GitHub templates under .github/ISSUE_TEMPLATE/ and a pull request template. New files: bug-report.yml (bug report form with required description, optional additional context and logs), feature-request.yml (feature request form with labels, required description, optional contribution intent and checklist), config.yml (issue template configuration allowing blank issues and a contact link), and .github/PULL_REQUEST_TEMPLATE.md (lightweight PR template with context, description, testing, and checklist sections).

Suggested reviewers

• danielroe

🚥 Pre-merge checks | ✅ 3 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Out of Scope Changes check	❓ Inconclusive	The PR introduces additional files (bug-report.yml, feature-request.yml, and config.yml) that extend beyond the PR template requirement in issue #1522.	Clarify whether bug report and feature request templates were part of the original scope. If they exceed issue #1522's scope, consider splitting into separate PRs or confirm they align with project standards.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description check	✅ Passed	The PR description clearly relates to the changeset by describing the addition of issue templates and PR templates for the Npmx project.
Linked Issues check	✅ Passed	The PR fulfils issue #1522 by adding a PR template with required sections like Context, Description, and a pre-PR checklist, though the exact structure differs slightly from the proposed template.
Merge Conflict Detection	✅ Passed	✅ No merge conflicts detected when merging into main

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

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

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

[coderabbitai]

Actionable comments posted: 3