Hello! I believe that the default policy (implemented by Infra) was to require a committer approval to launch CI on every PR.
In the recent past, every *new* contributor (who hadn't been approved before) required one approval, and in the farther past no PRs required approval. I think we're probably best off sticking with the INFRA defaults in general, but I really encourage committers to track and push the button on plausible PRs! I try to do this even if I don't have time to properly review that PR. I guess some projects have introduced a third role to try and emulate the behaviour where everyone who has contributed in the past can run CI. In an ideal world this would be pretty good, but adds some overhead! Maybe the simplest solution (in the meantime) is to create a PR against master in your *own* repo and run the CI personally! Can you give this a try and report if it works for you? All my best regards, Ryan On Wed, Jun 21, 2023 at 4:42 PM Christophe Le Saëc <chles...@gmail.com> wrote: > > Hello Avro developpers, > > A question on Avro Github Pull Request; since few weeks, i have some Java > PR, as this one <http://as this one>, where checks limits to "*Pull Request > Labeler / triage (pull_request_target)"*, and no compile/test are done. > Others PR, as this <https://github.com/apache/avro/pull/2268>, have a > complete check (spotless, Java8 compile/test ...), and i can't see > difference between (both have "Java" label ...). > > Is there any property i should put on PR to launch a complete check ? > > Regards, > Christophe.
