Hi, Infra did a commit that has “fixed” the trouble.
https://github.com/apache/echarts/commit/8ea10f4d0be0d97f3a89410c7daf16112cf3769c I think that putting all of the notifications into the commits@ list is sufficient. Regards, Dave > On Apr 9, 2022, at 3:12 AM, Yi Shen <shenyi....@gmail.com> wrote: > > +1 with Zhongxiang's proposal: > - iss...@echarts.apache.org (for issues) > - p...@echarts.apache.org(for pull requests) > - notificati...@echarts.apache.org(for various notifications like GitHub > actions) > > PS it should be done ASAP. > > On Sat, Apr 9, 2022 at 4:46 PM Ovilia <oviliazh...@gmail.com> wrote: > >> Hi all, >> >> We have been receiving a lot of automatic emails since 4th April in this >> mailing list. >> We are considering creating new mailing lists for these kinds of messages >> to prevent >> overwhelming messages. >> >> Zhongxiang has proposed the following names: [1] >> - iss...@echarts.apache.org (for issues) >> - p...@echarts.apache.org / pullreque...@echarts.apache.org (for pull >> requests) >> - notificati...@echarts.apache.org / j...@echarts.apache.org (for various >> notifications like GitHub actions) >> >> I would also like to hear about others' ideas. Whether we should create one >> single mailing >> list for issues, pull requests and actions all, or create three mailing >> lists. >> >> Thanks >> >> [1] https://github.com/apache/echarts/pull/16855 >> >> *Ovilia* >> > > > -- > Yi Shen > Apache ECharts PMC --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@echarts.apache.org For additional commands, e-mail: dev-h...@echarts.apache.org
