+1 to unleash this limitation. On Wed, Apr 12, 2023 at 3:04 PM jinrongtong <jinrongt...@apache.org> wrote:
> +1, It is inconvenient to need a maintainer to trigger CI every time. > At 2023-04-12 14:50:07, "aaron ai" <aaro...@apache.org> wrote: > >Recently, Apache Infra changed the trigger policy for GitHub actions from > >"requires approval for first-time contributors" to "requires approval for > >all outside collaborators". The motivation behind this change was to > >prevent the abuse of GitHub actions. However, I believe that this is a > >significant step backwards. RocketMQ has external contributors whose pull > >requests are now blocked until a maintainer manually approves the > >corresponding workflow, which creates a burden for both contributors and > >maintainers. > > > >I have created a Jira ticket > ><https://issues.apache.org/jira/browse/INFRA-24413> to track this issue > and > >request a return to the previous behavior of "requires approval for > >first-time contributors". We are willing to take responsibility for > >monitoring these workflows to prevent abuse. If you agree with my > viewpoint > >and would like to see a return to the previous policy, please use "+1" to > >express your support. If you disagree, please provide your reasons. We > want > >to hear from as many developers in the community as possible! > > > >Related link: > >* https://infra.apache.org/github-actions-policy.html > >* > > > https://github.blog/2021-04-22-github-actions-update-helping-maintainers-combat-bad-actors/ > > > >Thanks for your time, > >Aaron >
