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

   Since 2026-11-10 every asfyaml run on `main` has failed with:
   
       HTTPSConnectionPool(host='api.github.com', port=443): Max retries 
exceeded with url:
       /repos/apache/airflow/branches/main/protection (Caused by 
ResponseError('too many 502 error responses'))
   
   asfyaml applies its GitHub settings in order (`branch_protection` runs before
   `pr_creation_cap`) and stops at the first failure, and it only caches the 
settings
   after a full run. So every push to `main` retries and fails at the same 
point, and
   nothing after branch protection has been applied. That includes the creation 
cap
   `bypass_users` list from #76782: no one on that list has more than 5 open
   non-draft PRs, and new PRs from them since 2026-11-10 are drafts.
   
   This moves `main` from legacy `protected_branches` onto the "Branch 
protection"
   ruleset. That ruleset has enforced the same rules on the release branches 
since
   2026-10-23 (linear history, 1 approval, conversation resolution, no deletion 
or
   force-push). `protected_branches: ~` makes asfyaml delete the legacy rule, 
so it
   stops calling the failing endpoint. `main` keeps its "Require CI on main" 
ruleset.
   
   If GitHub also fails the DELETE of the legacy rule with a 502, the next run 
will
   still fail. In that case we can ask Infra to remove the legacy rule on 
`main` by
   hand.
   
   Related: apache/infrastructure-asfyaml#135, #76782
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes (please specify the tool below)
   
   Generated-by: Claude 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