This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch v3-4-test
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/v3-4-test by this push:
     new 6f3eb394cbf [v3-4-test] Add meel-ayush to fork CI pilot and exempt 
pilot users from PR cap (#76782) (#76813)
6f3eb394cbf is described below

commit 6f3eb394cbf7ff450895b23671289224999f2475
Author: Jarek Potiuk <[email protected]>
AuthorDate: Tue Nov 10 09:23:26 2026 +0100

    [v3-4-test] Add meel-ayush to fork CI pilot and exempt pilot users from PR 
cap (#76782) (#76813)
    
    * Add meel-ayush to fork-ci-gate pilot
    
    * Move meel-ayush pilot join date to 2026-11-11
    
    The previous instant is already in the past, which 
check-fork-ci-gate-config rejects.
    
    * Exempt fork CI pilot participants from the open PR limit
    
    Pilot participants run CI in their own forks, so their pull requests
    cost the project no runner time; the cap was meant to protect that.
    .asf.yaml can now set GitHub's bypass list 
(apache/infrastructure-asfyaml#135).
    
    (cherry picked from commit 6a8bc716a3940a8c95eb45412409293a832e551a)
    Generated-by: Claude Opus 5
---
 .asf.yaml                                        | 16 ++++++++++++++++
 .github/fork-ci-gate.toml                        |  1 +
 contributing-docs/32_open_pull_request_limit.rst | 11 +++++------
 3 files changed, 22 insertions(+), 6 deletions(-)

diff --git a/.asf.yaml b/.asf.yaml
index af7067281b2..530897dba74 100644
--- a/.asf.yaml
+++ b/.asf.yaml
@@ -86,6 +86,22 @@ github:
     creation_cap:
       enabled: true
       max_open_pull_requests: 5
+      # Exempt from the cap. This list replaces GitHub's bypass list on every 
sync, so users added
+      # by hand in the repository settings are removed. Fork CI pilot 
participants are exempt
+      # because their CI runs in their own forks; keep them in sync with 
[pilot] in
+      # .github/fork-ci-gate.toml.
+      bypass_users:
+        - aaron-y-chen
+        - Andrushika
+        - Dev-iL
+        - justinpakzad
+        - meel-ayush
+        - Prab-27
+        - raphaelauv
+        - SameerMesiah97
+        - sreecharan-desu
+        - stephen-bracken
+        - yuseok89
 
   # Legacy branch protection is being migrated to Rulesets below.
   #
diff --git a/.github/fork-ci-gate.toml b/.github/fork-ci-gate.toml
index f7a2a608fdc..1266287825a 100644
--- a/.github/fork-ci-gate.toml
+++ b/.github/fork-ci-gate.toml
@@ -50,3 +50,4 @@ job_statuses = true
 # check-fork-ci-gate-config hook rejects a new or changed instant that is in 
the past.
 [pilot]
 # "login-three" = 2026-10-20T00:00:00Z
+"meel-ayush" = 2026-11-11T00:00:00Z
diff --git a/contributing-docs/32_open_pull_request_limit.rst 
b/contributing-docs/32_open_pull_request_limit.rst
index 9c35bee274e..4dd370d0bea 100644
--- a/contributing-docs/32_open_pull_request_limit.rst
+++ b/contributing-docs/32_open_pull_request_limit.rst
@@ -157,12 +157,11 @@ where they were, and the Pull Request keeps its whole 
review history.
 Exceptions
 ----------
 
-GitHub supports a bypass list of users who are exempt from the limit. Support 
for configuring it
-through ``.asf.yaml`` is being added in
-`apache/infrastructure-asfyaml#135 
<https://github.com/apache/infrastructure-asfyaml/pull/135>`__.
-Until it is available, there are no exceptions. Once it is, maintainers may 
add contributors to the
-list where it makes sense - for example to let someone open an urgent fix 
while they are at the
-limit. If you think you need an exception, ask on the 
``[email protected]`` mailing list.
+Users listed under ``bypass_users`` in ``.asf.yaml`` are exempt from the 
limit. The list currently
+holds the participants of the fork CI pilot (the ``[pilot]`` section of 
``.github/fork-ci-gate.toml``),
+because the CI of their Pull Requests runs in their own forks. Maintainers may 
add other contributors
+where it makes sense - for example to let someone open an urgent fix while 
they are at the limit. If
+you think you need an exception, ask on the ``[email protected]`` 
mailing list.
 
 If you believe the limit was applied to you in error - for example your Pull 
Requests were closed by
 mistake - the appeal channel is the PMC private list; see the

Reply via email to