Hi, community.
Currently, we have completed the majority of tasks in the areas of [1] and [2]. However, I have noticed that the community still fails to fully adhere to certain standards when merging contributors' work [3], although this does not imply a lack of consensus among contributors, committers, and the community. Therefore, I have referenced [4] and introduced a boring-cyborg.yml[5] file for the StreamPark repository to improve this situation, This will help both contributors and committers clarify the adjustments needed to maintain consistency with [2] from the early stages of contributing (i.e., when submitting a PR). Due to permission limitations, I would appreciate the assistance of any PMC member to help complete certain tasks in order to finalize this improvement, including but not limited to: - Configuring the main StreamPark repository to activate the workflow defined in [5]. - Verifying the correctness of the configuration in [5]: - Whether the standardization of PR titles can be correctly validated. - Whether the PR ISSUE ID can be successfully linked to the corresponding ISSUE. - Whether the workflow can accurately label PRs with module information according to the locations of changes involved in the PR. Thank you. Best regards, Yuepeng Pan [1] https://github.com/apache/streampark/issues/2986 [2] https://streampark.apache.org/community/submit_guide/code_style_and_quality_guide [3] https://github.com/apache/streampark/commits/dev/?since=2025-08-01&until=2025-12-30 [4] https://github.com/apache/flink-connector-jdbc/blob/5ac251f90e803ea7cc8d35525237cf829efd2658/.github/boring-cyborg.yml [5] https://github.com/apache/streampark/pull/4320
