
21 Nov
2017
21 Nov
'17
12:36 a.m.
Ara Adkins
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. Cheers, - Ben