meel-ayush opened a new pull request, #76956: URL: https://github.com/apache/airflow/pull/76956
### Description Part of **AIP-120**: The fork CI reconciler previously treated edits to its own utility modules under `dev/breeze/src/` as gate tampering and closed contributor PRs with `gate_modified`, rather than treating them as CI-defining files that transition green runs to `green_unverified`. When contributors deleted their forks or changed account handles, missing head repositories caused the reconciler to emit an `unknown` finding that re-alerted Slack every 15 minutes indefinitely. Furthermore, manual `workflow_dispatch` re-runs in forks were ignored because only `push` events were collected, author reopens were disallowed even when gate changes were reverted, and failing fork runs had no inactivity closure path. This change: * Narrows `GATE_PROTECTED_PATHS` to `fork_ci_gate.py` and `fork-ci-monitor.yml` so reconciler edits follow normal CI verification and transition green runs to `green_unverified` with `needs project ci`. * Auto-closes deleted fork PRs with an explanatory comment instead of spamming Slack `#airflow-ci-alerts`. * Includes `workflow_dispatch` events when collecting check suites on the head commit so manual fork re-runs are recognized. * Allows author reopens on `gate_modified` PRs once gate changes have been removed, re-closing them only if gate changes remain. * Closes pull requests in `ForkState.FAILED` after 30 days of inactivity if no human comments have been posted. ### Tests - Unit tests added and updated in `dev/breeze/tests/test_fork_ci_reconcile.py` and `dev/breeze/tests/test_fork_ci_messages.py` covering author reopens, workflow_dispatch runs, deleted head repositories, and failing PR inactivity clocks. --- ##### Was generative AI tooling used to co-author this PR? - [ ] Yes (please specify the tool below) -- 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]
