potiuk opened a new pull request, #76243: URL: https://github.com/apache/airflow/pull/76243
Contributors enable Actions on their forks for fork CI (AIP-120), and every cron in the repository then fires in the fork too. The canaries already skip forks (`fork_schedule`), and the high-frequency crons (`spot-interruption-notice`, `auto-approve-workflow-runs`, `fork-ci-monitor`, `mirror-hardened-base-images`) are already guarded. Ten other scheduled workflows were not, so CodeQL and the maintenance jobs ran daily in each enabled fork on the contributor's minutes. GitHub has started disabling Actions on such forks to reduce wasted compute. This adds a job-level `github.repository == 'apache/airflow'` guard to them. Workflows with other triggers combine it with `github.event_name != 'schedule'`, so pushes, pull requests and manual dispatches still run in forks. The fork CI document now says that new scheduled workflows need the same guard. --- ##### Was generative AI tooling used to co-author this PR? - [X] Yes — Claude Code (Claude Opus 5) Generated-by: Claude Code (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]
