Change Pull Request Template

[klmhyeonwoo]

목적

• 풀리퀘스트 템플릿 변경

작업 내용

• 풀리퀘스트 템플릿을 변경했어요

필수 리뷰어

• N/A

Summary by CodeRabbit

• Chores
  • Updated the pull request template with new, clearly labeled sections and a mandatory reviewers list for improved organization and clarity.

[coderabbitai]

Walkthrough

The pull request modifies the pull request template file used for GitHub contributions. The update replaces the previous section headers, some of which were in Korean and English, with a new set of structured subsection headers, all in Korean. The new template introduces sections for purpose, work content, mandatory reviewers, issue number, and remarks, and explicitly lists three required reviewers. No code or exported/public entity changes were made.

Changes

File(s)	Change Summary
.github/pull_request_template.md	Replaced previous section headers with new structured Korean headers, added mandatory reviewers.

Poem

In the warren of code, a template anew,
With headers in order, and reviewers too!
Purpose and work, all clearly in sight,
Rabbits approve—this format feels right.
A hop and a skip, our process refined,
For every pull request, our efforts aligned!
🐇✨

Tip

⚡💬 Agentic Chat (Pro Plan, General Availability)

• We're introducing multi-step agentic chat in review comments and issue comments, within and outside of PR's. This feature enhances review and issue discussions with the CodeRabbit agentic chat by enabling advanced interactions, including the ability to create pull requests directly from comments and add commits to existing pull requests.

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (5)

.github/pull_request_template.md (5)

1-3: Add guidance for the '목적' section
The header is clear, but the bullet is empty. Consider adding a placeholder instruction so contributors know what to write (e.g., "이 PR의 목적을 간략히 작성하세요 (예: 버그 수정, 기능 추가 등)").

- ##### 목적
- - 
+ ##### 목적
+ - 이 PR의 목적을 간략히 작성하세요 (예: 버그 수정, 기능 추가 등)

---

4-6: Clarify the '작업 내용' section
Currently the bullet is blank. It may be helpful to include an example or prompt like "수행한 작업 내용을 상세히 작성하세요" to guide contributors.

- ##### 작업 내용
- - 
+ ##### 작업 내용
+ - 수행한 작업 내용을 상세히 작성하세요 (예: 주요 변경 사항, 기능 설명 등)

---

7-9: Standardize formatting of the reviewer list
The reviewers are listed on one line with inconsistent spacing around commas. For better readability, either list each reviewer on its own line or ensure consistent comma spacing.

- ##### 필수 리뷰어
- - @klmhyeonwoo, @Cllaude99 ,@joeunSong
+ ##### 필수 리뷰어
+ - @klmhyeonwoo
+ - @Cllaude99
+ - @joeunSong

---

10-12: Provide a placeholder for issue linking
The '이슈 번호' section is empty—consider showing how to reference an issue using GitHub syntax (e.g., "- #123" or "- flowbit-team/flowbit#123") so it's clear to contributors.

- ##### 이슈 번호
- - 
+ ##### 이슈 번호
+ - #<이슈 번호>

---

13-15: Explain the purpose of the '비고' section
The remarks section is currently empty. Adding a note like "추가로 알리고 싶은 사항이 있으면 작성하세요" will clarify when and how to use this field.

- ##### 비고
- - 
+ ##### 비고
+ - 추가로 알리고 싶은 사항이 있으면 작성하세요

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e044140 and 829995b.

📒 Files selected for processing (1)

• .github/pull_request_template.md (1 hunks)