ignore: add PR template

[Hona]

Summary

• Adds a pull request template to standardize PR descriptions
• Template sourced from Bun's repository

[github-actions]

Hey! Your PR title Add pull request template doesn't follow conventional commit format.

Please update it to start with one of:

• feat: or feat(scope): new feature
• fix: or fix(scope): bug fix
• docs: or docs(scope): documentation changes
• chore: or chore(scope): maintenance tasks
• refactor: or refactor(scope): code refactoring
• test: or test(scope): adding or updating tests

Where scope is the package name (e.g., app, desktop, opencode).

See CONTRIBUTING.md for details.

[Copilot]

Pull request overview

This PR adds a minimal pull request template to help standardize PR descriptions across the repository. The template prompts contributors to describe what their PR does and how they verified their changes work.

Key Changes:

• Adds a new PR template file in the .github directory with two prompting sections

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Consider adding a section for UI changes to prompt contributors to include screenshots or videos. According to CONTRIBUTING.md (lines 165-167), UI changes should include visual evidence showing before and after states. This could be a conditional section like "### Screenshots/Videos (if applicable for UI changes)".

Suggested change

	### How did you verify your code works?
	### How did you verify your code works?
	### Screenshots/Videos (if applicable for UI changes)

[Copilot]

The PR template is missing a section to prompt contributors to link to an existing issue. According to CONTRIBUTING.md (lines 152-157), there's an "Issue First Policy" stating that all PRs must reference an existing issue using "Fixes #123" or "Closes #123". Consider adding a section like "### What issue does this PR address?" to ensure contributors follow this requirement.

Suggested change

	### What issue does this PR address?
	<!-- Link to the issue using "Fixes #123" or "Closes #123". -->

[github-actions]

The following comment was made by an LLM, it may be inaccurate:

Based on my search, I found one potentially related PR:

PR #7013: fix(tool): require PR template check before creating PRs
#7013

This PR is related because it deals with PR template validation/requirements. While PR #7391 adds a new PR template and #7013 enforces checking for PR templates before creation, they may be complementary changes or there could be some overlap in scope depending on the implementation details.

The other results appear to be unrelated to the PR template feature.