Or, we can follow the template from the infra: ``` notifications: commits: comm...@foo.apache.org # Send all issue emails (new, closed, comments) to issues@ issues: iss...@foo.apache.org # Send new/closed PR notifications to dev@ pullrequests_status: d...@foo.apache.org # Send individual PR comments/reviews to issues@ pullrequests_comment: iss...@foo.apache.org ```
Just creating an issues mailing list is enough. On Mon, Sep 19, 2022 at 11:09 AM Xinyu Zhou <yu...@apache.org> wrote: > Hello, community, > > Recently, I found our dev mailing list is occupied by GitHub actions, > making it difficult to highlight critical emails. > > Since we already have a commits mailing list(comm...@rocketmq.apache.org), > how about directing GitHub actions to this mailing list? Or we can keep the > pull requests status notifications and direct other notifications to the > commits mailing list. > > Any discussions are welcome. > > Regards, > Xinyu Zhou > >
