<div dir="ltr">Do we have somewhere yet that we can start to look into an initial set of rules to discuss what the initial set should be?</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 10, 2019 at 6:32 AM Martin Stefanko <<a href="mailto:mstefank@redhat.com">mstefank@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">> The time the cross becomes a problem is if we adopt a set of verification rules that we know will regularly trigger a failure to be ignored, if the failure cases to be ignored are truly exceptional cases then the cross will be useful.<div><br></div><div>It would be beneficial to adjust rules as we'll see how useful they are as time progresses. Configuration of rules is external to the service so it will be possible.</div><div><div dir="ltr" class="gmail-m_1576121774971108453gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><br></div><div>Martin <br></div></div></div></div></div></div></div><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Apr 9, 2019 at 5:49 PM Darran Lofthouse <<a href="mailto:darran.lofthouse@jboss.com" target="_blank">darran.lofthouse@jboss.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div style="font-family:"trebuchet ms",sans-serif">> OTOH if the mergers decide they want to do something I don't want a tool preventing us doing it, which is what my questions were driving at. We're way smarter than the tool.</div><div style="font-family:"trebuchet ms",sans-serif"><br></div><div style="font-family:"trebuchet ms",sans-serif">The status should not prevent a possibility of merge but if the cross next to the commit would be a problem we can add an override to disable tyr check (meaning make it pass manually) with a comment or similar as suggested above.</div></div></blockquote><div><br></div><div>The time the cross becomes a problem is if we adopt a set of verification rules that we know will regularly trigger a failure to be ignored, if the failure cases to be ignored are truly exceptional cases then the cross will be useful.</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div dir="ltr" class="gmail-m_1576121774971108453gmail-m_39407116264145588gmail-m_8306954015641473860gmail_signature"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div><br></div><div>Martin<br></div></div></div></div></div></div></div><br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><br>
</blockquote></div>
</blockquote></div></div>
</blockquote></div>
</blockquote></div>