Hi,

Thanks for letting us know so many good tools.

I do not believe code changes by robots very much unless I read the code
changes myself.
But I also think having such tools can help us saving time.

- Mergify: I do not like it. :( I think it is dangerous...

- Dependabot: I like this tool. (But we'd better to have a full test, as
some dependencies may lead to performance reduction when it fixes
something.

- Codecov: Well, if someone can set this up, I opt for it! I have spent
more than 3 days to fix the coveralls... but failed. We need code coverage
checking very much.

- Imgbot: OK from my view, as we have few images in the repo.

- Pull Request Size: OK from my view.

- PEP 8 Speaks: I like it.

Best,
-----------------------------------
Xiangdong Huang
School of Software, Tsinghua University

 黄向东
清华大学 软件学院


Benedict Jin <[email protected]> 于2020年12月29日周二 下午3:35写道:

> Hi Justin Mclean,
>
> Yep, according to the experience in Apache Druid, we need to create a Jira
> in the Infrastructure project to enable robots. e.g,
> https://issues.apache.org/jira/browse/INFRA-18880
>
> Regards,
> Benedict Jin
>
> On 2020/12/29 06:04:40, Justin Mclean <[email protected]> wrote:
> > HI,
> >
> > How will these bots get access to the repos? Infra tightly controls what
> has access and it be be best to run it past Infra to see if they see any
> issues first with these bots.
> >
> > Thanks,
> > Justin
> >
> >
>

Reply via email to