chore(pr-template): Remove "Type of change" section

[woocheol-lge]

Description

chore(pr-template): Remove "Type of change" section

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: d40c6a72-5a9a-471a-a1ba-a5f127b0f49f

📥 Commits

Reviewing files that changed from the base of the PR and between b056754 and 516cf9f.

📒 Files selected for processing (1)

• .github/PULL_REQUEST_TEMPLATE.md

💤 Files with no reviewable changes (1)

• .github/PULL_REQUEST_TEMPLATE.md

---

📝 Walkthrough

Walkthrough

The "Type of change" section has been completely removed from the GitHub pull request template. This section previously contained checkbox options for categorizing PR types (Bug fix, New feature, Documentation update, Refactoring, Breaking change).

Changes

Cohort / File(s)	Summary
Pull Request Template .github/PULL_REQUEST_TEMPLATE.md	Removed the entire "Type of change" subsection including the header and all associated checkbox options for change classification.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and specifically describes the main change: removing the 'Type of change' section from the PR template.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ 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
• Commit unit tests in branch prtest

---

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