Hi Christofer Dutz, Thanks for your comments. I agree with you that we do need to fully understand and test a robot before introducing it. However, as far as I have listed, only some labels will be added and some PRs will be created, but they will not be merged automatically. Therefore, based on past experience, I personally feel that there is no need to worry too much. BTW, let me introduce a scene of the Mergify robot additionally. I see that we need to manually create some backport type PRs. In fact, Mergify can help us create them automatically. Automation not only frees hands, but also ensures the correctness of operation. FYI, https://github.com/apache/iotdb/pull/2357#issuecomment-751651306
Regards, Benedict Jin On 2020/12/28 09:19:59, Christofer Dutz <[email protected]> wrote: > Hi all, > > I would be careful about automating too much. > > The reason is that changes in the repo have to be an act of the projects > committers. By automating merges, dependency-updates and other stuff, we > would be technically making github or the apps a committer. We can't do that. > Especially it would be putting us at risk of getting unwanted stuff in. > > We can however use the tools to submit PRs with changes and provide > additional information, making things easier for us. > > Also you should probably give Apaches SonarCloud a spin. It has tons of > valuable information available in one place. > > Chris > > > > -----Ursprüngliche Nachricht----- > Von: Benedict Jin <[email protected]> > Gesendet: Montag, 28. Dezember 2020 08:44 > An: [email protected] > Betreff: Propose to use some robots provided in Github's Marketplace to help > us improve the efficiency of project maintenance > > Hello everyone, > > As the Apache IoTDB project continues to grow, the maintenance costs that > follow have gradually increased. In order to alleviate this problem, I > propose to use some robots provided in Github's Marketplace to help us > improve the efficiency of project maintenance. The following is a list of > some robots that I am familiar with, including the official website of the > plugin, some brief introductions, and case addresses. I hope it can trigger > more great ideas. Welcome to discuss and propose more useful robots. > > - [Mergify](https://github.com/marketplace/mergify) > - Mergify is a pull requests automation service. It allows you to trigger > actions when your pull requests match defined criteria. > - Example: https://github.com/crate/crate/pull/10881 > > - [Dependabot](https://github.com/marketplace/dependabot-preview) > - Dependabot can maintain your repository's dependencies automatically. > - Example: https://github.com/dependabot/dependabot-core/pull/2901 > > - [Codecov](https://github.com/marketplace/codecov) > - Codecov provides highly integrated tools to group, merge, archive and > compare coverage reports. > - Example: https://github.com/codecov/codecov-bash/pull/396 > > - [Imgbot](https://github.com/marketplace/imgbot) > - Imgbot is a friendly robot that optimizes your images and saves you time. > Optimized images mean smaller file sizes without sacrificing quality. > - Example: https://github.com/asdf2014/algorithm/pull/53 > > - [Pull Request Size](https://github.com/marketplace/pull-request-size) > - Each Pull Request created will be marked with a label in GitHub based on > the lines of code changed. > - Example: https://github.com/asdf2014/algorithm/pull/82 > > - [PEP 8 Speaks](https://github.com/marketplace/pep-8-speaks) > - PEP 8 Speaks is a GitHub app which detects Python code style issues on > new Pull Requests. > - Example: https://github.com/asdf2014/algorithm/pull/49 > > Regards, > Benedict Jin >
