Hello everyone,

Another status update. I believe - every point that cancelled the vote is
now fixed on main or in a pull request, and so are the problems pilot
participants reported on Slack and the points raised on this list.

>From the vote:

* Fork CI now tests the pull request merged into the target branch, as
project CI does. Every job merges the pushed commit with the target branch
commit fixed when the run starts, and a push that conflicts fails
immediately. Merged: https://github.com/apache/airflow/pull/77131

* "use project ci" and a green "CI passed": since
https://github.com/apache/airflow/pull/76672 the label holds "CI passed" at
pending until project CI passes. The new "breeze ci use-project-ci <PR>"
command holds it before adding the label, so there is no window in which
the pull request can merge on the fork result, and it restarts the pull
request so that project CI runs. "breeze ci use-fork-ci <PR>" moves it
back: https://github.com/apache/airflow/pull/77135

* Drafting on a failed run, the 30-day close window, "Startup Failure" and
late status were fixed earlier (#76681, #76835, #76836).

>From the pilot and this list:

* Job statuses: passed jobs are counted in "Fork CI / Tests (AMD)" instead
of getting a status each, cancelled jobs get one status, and the monitor's
write budget follows the real time between its runs:
https://github.com/apache/airflow/pull/77125

* A maintainer's approving review of a pull request's latest commit also
approves its waiting CI runs, as Iliya suggested:
https://github.com/apache/airflow/pull/77134

* Documentation: the contributor docs keep what contributors need, the
design document is the maintainer reference, and the other guides link to
them instead of repeating them: https://github.com/apache/airflow/pull/77133

* The monitor's alerts say why a GitHub call failed:
https://github.com/apache/airflow/pull/77132

* Merged in the meantime: inactive pull requests are no longer closed while
they get commits, reviews or discussion (#76956), conflicting pushes fail
early (#76955), and scheduled workflows stay off in forks (#76267).

So far 9 of the 11 pilot participants have opened 50 pull requests under
fork CI, and 30 of them have merged.

Thanks to everyone who took part in the pilot, and still does: Iliya Romm,
Andrew Chang, Aaron Chen, Justin Pakzad, Sameer Mesiah, Pratiksha Badheka,
SreeCharan Desu, Stephen Bracken, raphaelauv, Yuseok Jo and Ayush Meel.
Most of these fixes came from your pull requests and your reports on Slack.

Please review #77125 (already approved), #77132, #77133, #77134 and #77135.
Once they are merged, I would ask the pilot participants to keep working as
usual for a day and report anything odd, so that we re-test everything
together.

The ADIP-12 page describes fork CI with all of these merged. It also
answers two open questions: stakeholder exemptions are granted when the PMC
trusts the stakeholder not to abuse them, each confirmed by a vote on
private@, and the cost spread between a documentation change and a full run
is about 142x:
https://cwiki.apache.org/confluence/spaces/AIRFLOW/pages/451974711

I intend to call the new [VOTE] in a day or so, after the re-test.

As asked in the first vote, the vote email will say up front that some pull
requests will be merged on fork CI results without a project CI run, what
problem this solves, and where the trust boundaries are.

If anyone still has questions or doubts, this is the right time to raise
them.

J.

On Tue, Nov 10, 2026 at 10:37 PM Jarek Potiuk <[email protected]> wrote:

> Hello everyone,
>
> A status update on the points that cancelled the vote. Two are fixed
> on main, and the rest are in pull requests that need reviews:
>
> * Fork CI tests the tip of the branch, not the pull request merged
> into the target branch: https://github.com/apache/airflow/pull/76837 —
> "CI passed" is reported only for a recent base that changed none of
> the pull request's files, and the state comment shows the base the run
> was tested on.
> * "use project ci" does not withdraw a green "CI passed":
> https://github.com/apache/airflow/pull/76672 (Shahar, in progress).
> * Pull requests drafted on the first failed run, and the 7-day close
> window: merged in https://github.com/apache/airflow/pull/76681 — a
> failed run no longer drafts the pull request, and inactive pull
> requests close after 30 days.
> * "Startup Failure" not shown on the pull request, and the bot linking
> the design document: https://github.com/apache/airflow/pull/76835
> * Status arriving late and with little detail:
> https://github.com/apache/airflow/pull/76836 — the monitor runs every
> 5 minutes, and a failed run lists the jobs that failed.
> * Diagrams: a pull request lifecycle diagram in the docs
> (https://github.com/apache/airflow/pull/76839), and the architecture,
> state and lifecycle diagrams generated from one source by a prek hook,
> for both the docs and the wiki
> (https://github.com/apache/airflow/pull/76841).
>
> The ADIP-12 page (formerly AIP-120) now has the status of each point,
> those diagrams, and a section on why this is more secure than running
> project CI for every pull request:
> https://cwiki.apache.org/confluence/spaces/AIRFLOW/pages/451974711
>
> Reviews and comments are very welcome, on the pull requests or here,
> especially from maintainers who merged pull requests under fork CI and
> from anyone who tried the pilot. I will call the new vote once these
> are merged and tested in the pilot.
>
> J.
>

Reply via email to