Define PR naming convention

[yhilmare]

Let us define our pr naming convention, and there is a proposal:

[type][scope] Summary

Here is an example: apache/pulsar#21048

• type: feat | improve | fix | cleanup | refactor | revert
• scope: connect | session | flow
• Summary: Explicit and self-explanatory. A complete sentence in present tense imperative. Capitalize 1st letter. No period at the end

[yhilmare]

Or we can maintain our current naming convention:

type(scope): summary

[yhilmare]

There are two options:

1. https://www.conventionalcommits.org/pt-br/v1.0.0/
2. http://karma-runner.github.io/6.4/dev/git-commit-msg.html

[whhe]

I think we can keep the current naming convention since most GitHub actions on the marketplace work with it.
https://github.com/marketplace/actions/semantic-pull-request
https://github.com/marketplace/semantic-prs

[yhilmare]

Thanks 4 reply, we discussed offline and decided to keep our current pr template, just like this: http://karma-runner.github.io/6.4/dev/git-commit-msg.html