Should we send Travis messages to ghc-builds?

Hello everyone, While picking up the pieces from a failed merge today I realized that we currently spend a fair bit of carbon footprint and CPU cycles making Travis test GHC yet the results of these tests aren't pushed anywhere. Would anyone object to having Travis push notifications of changes in red/green state to ghc-builds@haskell.org? Perhaps this will allow some of us to react more quickly to regressions. Cheers, - Ben