potiuk opened a new pull request, #74909:
URL: https://github.com/apache/airflow/pull/74909

   Stacked on #74825. Part 6 of the AIP-120 implementation (design: #73378); 
this PR's base is the previous branch, so the diff shows only this layer.
   
   Follow-ups to the reconciler in #74822, one commit each, plus protection of 
the gate itself:
   
   - A "push again" nudge is posted before the state comment records 
`awaiting_push`, so a failed post is retried.
   - A workflow or trigger the base branch does not have counts as project CI 
in the tampering check only if one of its jobs ran.
   - Pull requests sharing a head commit across different bases stay 
`green_unverified`, since one commit status cannot hold a decision per base.
   - Recorded runs made while the pull request targeted a base without the gate 
are ignored; a run that could belong to another pull request from the same 
branch is reported to Slack instead of closing.
   - A gated pull request that changes the fork CI gate (gate code, 
configuration beyond the author's own `[pilot]` entry, the `gate` job or its 
wiring in `ci-amd.yml`, or the monitor) is closed with a comment explaining 
why. Each of those files says so. The state comment's marker records 
`gate_checked` only when this check ran for the head commit, so pull requests 
reconciled before it existed are checked once.
   
   closes: #74905
   closes: #74906
   closes: #74907
   closes: #74908
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Claude Code (Opus 5)
   
   Generated-by: Claude Code (Opus 5) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)
   


-- 
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]

Reply via email to