search for: ibiryukov

...sic missing functionality > like notifications. > > Ilya, can you forward whatever ticket or tracking entry there is here? I'd > love to try and surface the critical nature of this for the LLVM project to > GitHub folks. > > On Tue, Jan 15, 2019 at 8:03 AM Ilya Biryukov <ibiryukov at google.com> > wrote: > >> The script queries **all** issues with specified labels and "notifies" on >> each of those. >> While this approach works, I doubt it would scale well if everyone is >> doing this by hand. OTOH, building a service that does this...

The script queries **all** issues with specified labels and "notifies" on each of those. While this approach works, I doubt it would scale well if everyone is doing this by hand. OTOH, building a service that does this for everyone might be feasible, albeit non-trivial and it's not clear who should own this. So overall having this supported by GitHub would mean a much better UX...

PaulR (sorry again if this is known knowledge) > There's no reason for Herald to be adding project LLVM/subscriber llvm-commits at the last second here. Its possible the rL (LLVM) had be added as the repository in the review on creation rather than rCFE, if thats the case then the herald rule "H270" is going to fire because it see the repository in the review, so add LLVM

On Sat, Jun 1, 2019 at 5:29 AM <paul.robinson at sony.com> wrote: > One particular change: I've disabled notifications for the duplicate > Subversion meta-repos... so, for example, a commit to Clang will still get > 2 notifications (rL and rG). Before yesterday, this should have sent 3: one > each for rL, rG, and rC. Projects not in the monorepo will get > notifications