On 06/10/2015 06:05 PM, Michael Still wrote:
> I think its fine for you to not want merge conflict messages from
> third party CI systems, but I do think we need to note that many of
> them do this now -- turbo hipster for example. If we turn off that
> message, then those CI systems will silently
Actually, and I think this was the point Sean was making, zuul
supports a different configuration for merge-failures which means CI
systems don't need to message back on merge-failures but can still
message back on real failures.
I'll look at changing turbo-hipsters reporting.
Cheers,
Josh
On Th
I think its fine for you to not want merge conflict messages from
third party CI systems, but I do think we need to note that many of
them do this now -- turbo hipster for example. If we turn off that
message, then those CI systems will silently fail and we will need to
be better at noticing that t
