Hello, There seems to be no objections on this so I've sent PR implementing this for all (active) Mynewt repositories: https://github.com/apache/mynewt-nimble/pull/1814 https://github.com/apache/mynewt-mcumgr/pull/174 https://github.com/apache/mynewt-newt/pull/564 https://github.com/apache/mynewt-newtmgr/pull/210 https://github.com/apache/mynewt-site/pull/549 https://github.com/apache/mynewt-documentation/pull/118 https://github.com/apache/mynewt-blinky/pull/25 https://github.com/apache/mynewt-artifact/pull/38 https://github.com/apache/mynewt-nffs/pull/21
On Mon, 22 Jul 2024 at 17:37, Szymon Janc <szymon.j...@codecoup.pl> wrote: > Hello, > > This email is to discuss on how various github notifications are handled > (since github is mostly used to project development discussions) > > Based on boards feedback and some discussions on CoC EU I suggest to go > with following: > - when PR is merged notification is sent to commits@ > - github issues and PR comments are sent to notifications@ > > This allows anyone to easily track what code goes in while also filter > messages of interest > and also provides proper archiving via ASF mailing lists. > > > PR that implements it for mynewt-core reposotory is here [1]. If there > will be no objections in > week or two I'll prepare similar PRs for other repositories and merge them. > > [1] https://github.com/apache/mynewt-core/pull/3290 > > -- > pozdrawiam > Szymon K. Janc > -- pozdrawiam Szymon K. Janc
