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

   Amazon, Google and Astronomer maintain large parts of Airflow and open many 
PRs from their own repositories. Those PRs often touch large providers or CI, 
so they fail the size and CI-definition rules and wait for a maintainer on 
every push, even though only people the stakeholders gave write access can push 
their commits.
   
   The workflow-run approver now always approves the runs of PRs from these 
repositories:
   
   | Repository | Stakeholder |
   |---|---|
   | `astronomer/airflow` | Astronomer |
   | `aws-mwaa/upstream-to-airflow` | Amazon |
   | `VladaZakharova/airflow` | Google |
   
   Notes for reviewers:
   
   - Repositories are matched by their numeric GitHub id, not their name, so a 
repository that later takes over one of these names after a rename or deletion 
is not trusted.
   - Trusted PRs skip every other rule, including the CI-definition check 
(`.github/`, `dev/breeze/`, `scripts/ci/`) and the release-branch rule. That is 
intended: trust goes to whoever has write access to these repositories. 
`VladaZakharova/airflow` is a personal repository, so for Google that trust 
depends on its owner's collaborator list.
   - The 24-hour run window still applies. When several open PRs share a 
trusted head commit, each run is approved once.
   
   ---
   
   ##### 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