github-actions[bot] opened a new pull request, #76307:
URL: https://github.com/apache/airflow/pull/76307

   * Check the fork's GitHub Actions settings in breeze ci audit
   
   breeze ci audit checked only that the fork's ci-amd.yml workflow is
   active. A workflow can be active while GitHub Actions is disabled for
   the whole fork: then a push starts no run, and the audit still said ok.
   Actions can also allow only the owner's actions or a selected list:
   ci-amd.yml uses actions from other repositories, so its runs fail
   before any job starts.
   
   For a contributor who needs fork CI, the audit now reads the fork's
   Actions settings and fails when Actions is disabled or limited, with
   the command that enables all actions. Only the fork's owner can read
   these settings, so the fork CI monitor cannot check them.
   
   * Report fork Actions settings whatever the CI workflow's state
   
   Check 5 used the Actions settings only when Tests (AMD) was active.
   A fork whose workflow was inactive, or whose workflow could not be read,
   was never told that Actions was disabled or limited. Enabling the
   workflow alone still left it unable to run, and the Actions problem
   showed up only on a later audit, if at all.
   
   Generated-by: Claude Opus 5
   
   * Detect a fork paused by GitHub and its idle workflows in breeze ci audit
   
   GitHub can pause GitHub Actions in a fork to reduce wasted compute.
   The fork's settings then still read as enabled and ci-amd.yml as
   active, so check 5 passed while no push started a run. Check 5 now
   dispatches ci-amd.yml to a ref that cannot exist: GitHub answers "No
   ref found" when Actions can run and "Actions has been disabled" when
   it is paused. Git does not allow ".." in a ref name, so the dispatch
   never starts a run.
   
   A fork that enables Actions also gets every cron of the repository,
   and each one starts a run there even when its jobs are skipped. The
   new check 8 lists the workflows that only a schedule or another
   workflow's run starts, and --fix disables the ones still active in
   the fork. Fork CI runs on push and does not need them.
   
   ---------
   (cherry picked from commit 1d5644d9de225b9205bc5b5308ac273dfb941f2d)
   
   Co-authored-by: Andrew Chang <[email protected]>
   Co-authored-by: Jarek Potiuk <[email protected]>


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