Hmm, it might be good, but it increases the infra costs. Given that contributors are expected to fork and enable CI on their forked repo, they can check the CI there as well.
I feel like the current model - while being a bit restrictive on contributors - is still good for keeping costs in check. We could improve the documentation on this in the contributing guide (make these points explicit that the contributors can check their forked CI for status) and the same could be attached to the PR (probably a description on the PR template saying edit and attach forked CI status if applicable?) On Sun, Aug 2, 2026 at 12:42 PM Wei-Chiu Chuang <[email protected]> wrote: > Hi Ozone developers, > > The Apache Infra's default policy allows GitHub Actions only for > committers. This is not friendly to our contributors. Apache Infra has an > alternative rule to"only require approval first time". I've not used it > before so I'm unsure how useful it is, but I wanted to raise it so we can > consider moving to that model in the future. > > Reference: https://infra.apache.org/github-actions-policy.html >
