Hi,
cancai. Thank you for your attention on this section.
In my limited read, This may require the following limitations. Perhaps we
have to make some necessary trade-off.
- The plugin that uses the commit header format verification will fail to
verify ci as long as it does not conform to the format.
As far as I know, pravega[1] currently uses this strategy, but I'm
a bit worried that overly complex or strict restrictions may affect the
enthusiasm of sharers
- Committers adheres to these rules[2] during the review and merge
operations to ensure reasonable formatting.
Looking forward to more ideas about it~
[1] https://github.com/pravega/pravega
[2]
https://streampark.apache.org/community/submit_guide/code_style_and_quality_guide#1-pull-requests--changes-rule
Best,
Roc.
At 2024-01-06 20:21:05, "caican cai" <[email protected]> wrote:
>Hello everyone, since joining the Streampark community, I have observed
>that PR submissions in the Streampark community are very irregular, which
>is very unfavorable for regulation and new developers to learn. For
>example, the PR title should be limited to the words [Fix], [Feature], etc. The
>first letter of words should be capitalized. We should also add words such
>as [Hotfix] including some simple repairs. I would like to ask your opinion.
>
>Best wish,
>Caican Cai
