Remove "Type of change" section from PR default template

[woocheol-lge]

Description

Remove "Type of change" section from PR default template

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request removes the "Type of change" section from the pull request template file, simplifying the template structure. This involves deleting checkbox options previously available for contributors to categorize their contributions.

Changes

Cohort / File(s)	Summary
Pull Request Template .github/PULL_REQUEST_TEMPLATE.md	Removed the "Type of change" section containing checkbox options; template now concludes with a closing comment marker. Net change: 1 line added, 13 lines removed.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 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, which aligns perfectly with the actual modifications shown in the raw summary.
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 github_template

---

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

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

.github/PULL_REQUEST_TEMPLATE.md (1)

1-4: No automation dependencies found on the removed section.

The search found no automation, scripts, or workflows that depend on the "Type of change" section. However, CONTRIBUTING.md still references adding labels based on "type of changes" (line 11), which creates a minor documentation-template inconsistency. Consider clarifying the contribution guidelines to align with the simplified template or documenting where contributors should determine change types.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In @.github/PULL_REQUEST_TEMPLATE.md around lines 1 - 4, Update CONTRIBUTING.md
to remove or clarify its reference to adding labels based on the "Type of
change" section (mentioned at the top of the PR template) so it matches the
simplified .github/PULL_REQUEST_TEMPLATE.md; specifically, change the guidance
that currently instructs contributors to add labels from a "Type of change"
section to instead explain the new process for determining change types (e.g.,
list the labels and where maintainers will apply them or instruct contributors
to indicate change type in the PR description), and ensure the document mentions
the PR template title "Type of change" if you choose to keep an explicit field.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/PULL_REQUEST_TEMPLATE.md:
- Line 4: The file .github/PULL_REQUEST_TEMPLATE.md is missing a trailing
newline; open the file and add a single newline character at the end of the file
(ensure the file ends with '\n') so the repository follows POSIX text file
conventions and avoids linting/CI warnings.

---

Nitpick comments:
In @.github/PULL_REQUEST_TEMPLATE.md:
- Around line 1-4: Update CONTRIBUTING.md to remove or clarify its reference to
adding labels based on the "Type of change" section (mentioned at the top of the
PR template) so it matches the simplified .github/PULL_REQUEST_TEMPLATE.md;
specifically, change the guidance that currently instructs contributors to add
labels from a "Type of change" section to instead explain the new process for
determining change types (e.g., list the labels and where maintainers will apply
them or instruct contributors to indicate change type in the PR description),
and ensure the document mentions the PR template title "Type of change" if you
choose to keep an explicit field.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 9393f625-146f-4063-946c-77bae7e54cc6

📥 Commits

Reviewing files that changed from the base of the PR and between 6ab6c87 and 72b9a59.

📒 Files selected for processing (1)

• .github/PULL_REQUEST_TEMPLATE.md