potiuk commented on PR #75142: URL: https://github.com/apache/airflow/pull/75142#issuecomment-6383188378
Merge order with AIP-120: this PR goes in first, the fork CI stack (#74819 → #74825) after it. Until #74819 adds its condition to `build-info`, the gate job always reports as "CI passed", and the "CI passed (project CI not run)" name only starts to appear once the fork CI gate lands. From then on the fork CI reconciler (#74822) posts the "CI passed" status for PRs whose fork run is green and trusted, so gated PRs can auto-merge too. I verified the two GitHub behaviours this relies on in a scratch repo with the same ruleset shape: - `gh pr merge --squash --auto` run by a ruleset bypass actor while the required check is in progress does **not** merge immediately - the PR stays BLOCKED and merges once "CI passed" is green. - A failing "CI passed" check run is not overridden by a successful "CI passed" commit status from `github-actions` on the same commit - the PR stays BLOCKED. So the reconciler's status cannot mask a red project CI run (e.g. after "use project ci"). --- Drafted-by: Claude Code (Claude Opus 5.5); reviewed by @potiuk before posting -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
