Maybe we should set some PR rules

[thelightway24]

Hi all 👋

I think we need some rules for PRs.
Today I talked with the maintainer about commit history management over a coffee chat.
But the maintainer is very busy, so managing it directly might not be easy.
That’s why I thought: why don’t we set some PR rules?

For example, when we work on code, we often end up with many commit logs.
Contributors could use git rebase to clean them up.
Then the maintainer would only need to merge.

I see this as a good starting point for collaboration 🤝
Contributors only need to polish and organize a single PR,
but maintainers have to manage many PRs at once.

I think it would be helpful to have branch naming rules and PR title rules as well.
These make changes easier to understand at a glance,
and they could also help with repository management via automation.

I’d love to hear your thoughts 💬

See also: https://www.conventionalcommits.org/ko/v1.0.0/

[owjs3901]

I agree. First, we should decide where to write the PR rules.

[thelightway24]

Here are my suggestions for the PR Rules:

• We could create a separate PR_RULES.md and link it in the CONTRIBUTING.md guide.
• Alternatively, a new GitHub Wiki (separate from /docs) would also work well.
• We should also add a note to the PR template itself, reminding contributors to read the rules.

[owjs3901]

I agree, and we would create github action to check PR_RULE