Hi all, Currently in our community, non-Committer contributors cannot actively trigger CI when contributing PRs to IoTDB. It requires a Committer to click to trigger CI, which causes some inconvenience.
By learning and understanding the Apache standards[1], we found that each repository can allow up to 10 non-Committers to trigger CI when submitting PRs. In addition, there are already Apache projects (such as Apache Doris[2]) that have done similar work[3]. In order to enhance the open-source experience for non-Committer contributors, we would like to provide the convenience of automatically running CI after submitting PRs for contributors with the following characteristics: 1. Have consistently contributed to IoTDB with more than 5 commits in the past 12 months[4]. 2. Are expected to continue to contribute to IoTDB in the next 12 months. 3. Do not misuse IoTDB's CI resources for illegal matters (such as mining, etc.). Contributors who wish to become part of the above group, please reply to this email with your Github ID and the number of commits you have contributed in the past 12 months. If there are more than 10 contributors responding, it may be sorted by the number of commits from high to low and select the top 10 contributors. It is expected that this email will last for about a week. Next week, I will summarize the emails, calculate the results, and initiate the final round of public announcement. If there are no issues, I will submit a PR. [1] https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INFRA&title=Git+-+.asf.yaml+features#Git.asf.yamlfeatures-AssigningexternalcollaboratorswiththetriageroleonGitHub [2] https://github.com/apache/doris [3] https://github.com/apache/doris/blob/master/.asf.yaml#L131 [4] https://github.com/apache/iotdb/graphs/contributors Best ------------- Xinyu Tan Apache IoTDB PMC On 2024/08/19 14:46:23 Christofer Dutz wrote: > Running that on the master branch in the CI wouldn’t be helpful, as the CI > shouldn’t be allowed to commit changes to the codebase. > That’s why I’m suggesting calling the “apply” instead of the “check” goal in > our build. > > Chris > > Von: liyuheng <liyuheng55...@126.com> > Datum: Montag, 19. August 2024 um 15:02 > An: dev@iotdb.apache.org <dev@iotdb.apache.org> > Betreff: Re: [DISCUSS] How about running spotless:apply instead of > spotless:check in the build? > Hi, Chris > > Auto spotless is a great idea. For my opinion, we can do auto spotless in > master branch one time every day, and remove other spotless check. > > And +1 for spotless is still necessary. >
