... +1 (Michael) ... and: if you botch your own PR build you are already notified automatically (which is quite a lot when all Github Workflows fail).
On Sun, Mar 27, 2022 at 9:21 PM Michael Vorburger <[email protected]> wrote: > I would NOT enable this, because getting emails on this mailing list for > each failed build using GitHub Actions, or a change from failure in > previous builds to a successful build, is probably too "noisy" here. > > > On Sat, Mar 26, 2022 at 11:54 PM Awasum Yannick <[email protected]> wrote: > >> >> >> ---------- Forwarded message --------- >> From: Daniel Gruno <[email protected]> >> Date: Sat, Mar 26, 2022, 21:58 >> Subject: [NOTICE] Introducing GitHub Actions build status notification >> for git repositories. >> To: <[email protected]> >> >> >> Dear Apache projects, >> We are happy to announce yet another feature in our beloved .asf.yaml >> file, namely GitHub Actions build status emails. As the name suggests, >> these are emails that notify of either a failed build using GitHub >> Actions, or a change from failure in previous builds to a successful >> build. Continuously successful builds will not trigger emails, as that >> could be rather spammy. >> >> If your project uses GitHub Actions and wishes to enable status >> notification emails, please see our documentation on this at: >> https://s.apache.org/asfyaml-gha >> >> In short, what you need to do is add a 'jobs' directive to your existing >> notifications section in .asf.yaml if you have such a file (or create it >> if you want this feature), for example: >> >> notifications: >> jobs: [email protected] >> >> We hope this feature will help our projects, and look forward to any >> feedback you may have, at: [email protected] >> >> With regards, >> Daniel on behalf of the ASF Infra Team. >> >> >> PS: Do note that this does not apply to subversion mirrors on GitHub, >> as .asf.yaml is not enabled for these repositories. >> >>
