Commit Notifications Flood

Ben Gamari ben at
Tue Nov 21 00:36:26 UTC 2017

Ara Adkins <me at> writes:

> I've put a redirect rule on them for now, but given that this is the second
> time that it's happened (as far as I know), is it possible to modify the
> way in which the commit hook sends notifications for new branches with a
> significant history? I don't really know much about the exact message
> generation process, but perhaps it is possible to provide a digest when
> pushing a new branch. Something that lists the branch name and the number
> of commits, for example.
Indeed we really should set an upper bound on the number of messages
that it will send. I agree that this is quite ridiculous.


- Ben

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
URL: <>

More information about the ghc-devs mailing list