<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Also the how to submit which is linked:</div><div><br></div><div><a href="https://developer.jboss.org/wiki/HackingOnWildFly">https://developer.jboss.org/wiki/HackingOnWildFly</a></div><div><br>On Sep 3, 2015, at 4:40 PM, Tomaž Cerar <<a href="mailto:tomaz.cerar@gmail.com">tomaz.cerar@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div><div>there was recent post on this mailing list on exact this topic.<br><br></div>this was outcome:<br><a href="https://developer.jboss.org/wiki/WildFlyPullRequestStandardsAndGuidelines">https://developer.jboss.org/wiki/WildFlyPullRequestStandardsAndGuidelines</a><br><br><br>--<br></div>tomaz<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 3, 2015 at 8:48 PM, Aleksandar Kostadinov <span dir="ltr"><<a href="mailto:akostadi@redhat.com" target="_blank">akostadi@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Is there any document describing wildfly PR review process? Blog, diagram, etc.<div><div class="h5"><br>
<br>
Tomaž Cerar wrote on 09/03/2015 07:25 PM:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
Hey guys,<br>
<br>
this mail is just heads up about recent changes to our CI <--> GitHub<br>
PR integration.<br>
<br>
As we started adding more and more different jobs to test each PR number<br>
of comments<br>
on each PR became almost like spam as each job added one comment when it<br>
started<br>
and second one with report of the build.<br>
<br>
With changes we did in past few weeks, we now have:<br>
<br>
- all build statuses only as part of github PR status check [1]<br>
- comments get added only when there is build failure<br>
- usual, retest this please & friends still work as they use to<br>
- *in testing* auto lableling / unlabling of rebase-this/fixme lables.<br>
<br>
So to see the actual status of the builds and if all checks passed,<br>
you will need to look at the pull request itself and not only mail<br>
notifications like till now.<br>
<br>
--<br>
tomaz<br>
<br>
<br>
[1]<br>
<a href="https://github.com/blog/1935-see-results-from-all-pull-request-status-checks" rel="noreferrer" target="_blank">https://github.com/blog/1935-see-results-from-all-pull-request-status-checks</a><br>
<br>
<br></div></div>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a><br>
<br>
</blockquote>
</blockquote></div><br></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>wildfly-dev mailing list</span><br><span><a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a></span><br><span><a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></span></div></blockquote></body></html>