You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ozone.apache.org by Wei-Chiu Chuang <we...@apache.org> on 2026/08/02 07:12:25 UTC

Trigger CI for non-committers' PR

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

Re: Trigger CI for non-committers' PR

Posted by Ethan Rose <er...@apache.org>.
Note that the ASF's policy is actually from a security perspective, as
commits can potentially exfiltrate secrets or run  malicious jobs. With AI
it is easier than ever for a motivated attacker to put in legitimate
patches before acting. See the xz hack for an extreme example of this
behavior. In that sense I don't think clearing the "first time conributor"
bar is enough to warrant access to ASF CI resources.

I actually think we should push for less CI running in the main apache repo
anyways. The apache repo is where it costs the ASF money. CI running on the
contributor's fork is identical to upstream and only one extra click away
for reviewers.

Regardless of committership it would be nice if we had a way to prevent any
CI from running in apache until PRs are approved, relying only on the
fork's CI during the review process. If github doesn't support this OOTB we
could probably create a label and job that handles it. Draft mode is a
workaround because it also communicates that a PR is not ready for broad
review.

Ethan

On Sun, Aug 2, 2026 at 5:07 AM Attila Doroszlai <ad...@apache.org>
wrote:

> > 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)
>
> It is already documented:
>
> https://github.com/apache/ozone/blob/a481e65272a67182c812e4c042a4518a2a638df2/CONTRIBUTING.md#contribute-your-modifications
>
> > 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?)
>
> Agree, the PR template should be improved.
>
> -Attila
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ozone.apache.org
> For additional commands, e-mail: dev-help@ozone.apache.org
>
>

Re: Trigger CI for non-committers' PR

Posted by Attila Doroszlai <ad...@apache.org>.
> 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)

It is already documented:
https://github.com/apache/ozone/blob/a481e65272a67182c812e4c042a4518a2a638df2/CONTRIBUTING.md#contribute-your-modifications

> 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?)

Agree, the PR template should be improved.

-Attila

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ozone.apache.org
For additional commands, e-mail: dev-help@ozone.apache.org


Re: Trigger CI for non-committers' PR

Posted by Abhishek Pal <ab...@apache.org>.
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 <we...@apache.org> 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
>