[ISSUE #6629] Rewrite the issue/PR template of RocketMQ

[aaron-ai]

Fixes #6629

[codecov-commenter]

Codecov Report

Merging #6645 (6a406a4) into develop (652f5bb) will increase coverage by 43.08%.
The diff coverage is n/a.

@@              Coverage Diff               @@
##             develop    #6645       +/-   ##
==============================================
+ Coverage           0   43.08%   +43.08%     
- Complexity         0     8990     +8990     
==============================================
  Files              0     1107     +1107     
  Lines              0    78307    +78307     
  Branches           0    10208    +10208     
==============================================
+ Hits               0    33742    +33742     
- Misses             0    40343    +40343     
- Partials           0     4222     +4222     

see 1107 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[RongtongJin]

Do we need to add templates like 'enhancement' in addition to 'bug_report' and 'feature_request'? For example, for typo fixes or small optimizations that may not be big enough to be considered a feature request.

[aaron-ai]

Do we need to add templates like 'enhancement' in addition to 'bug_report' and 'feature_request'? For example, for typo fixes or small optimizations that may not be big enough to be considered a feature request.

Nice idea! I will add a new template about it.

[aaron-ai]

@RongtongJin I have already added the template of enhancement.

An issue should be considered as an enhancement when it proposes improvements to existing functionality or user experience, without necessarily introducing new features or fixing existing bugs.

By the way, I believe typos should be classified as bugs rather than enhancements; the criteria for an issue to be classified as an enhancement is very strict. Most of issues should be classified as bug or feature request.

[zhouxinyu]

Looks great.