zhangshenghang commented on PR #13204: URL: https://github.com/apache/seatunnel/pull/13204#issuecomment-6765973667
Root cause found for the missing Build runs — it is repo/account level, not a lost trigger: - Fork Actions state via API: `actions/permissions` reports `enabled: true, allowed_actions: all`, and every workflow is `active`. We toggled the flag off and on via the API — the setting takes effect — yet `POST /actions/workflows/build_main.yml/dispatches` still returns **HTTP 422 "Actions has been disabled for this repository"** for any branch. - All pushes since 2026-11-06 22:36 (real commits and empty "Trigger CI" commits, from this account) produced zero workflow runs. That is why empty commits cannot help, as you suspected. So GitHub considers Actions disabled for this fork despite the permissions endpoint claiming otherwise — which points at the **user-level Actions spending limit / billing hold** (the same suspect you named). The billing endpoints (`/user/settings/billing/actions`) are not reachable with this token, so this needs the account owner in the web UI: **Settings → Billing and plans → spending limit for Actions**, and/or the fork's Settings → Actions toggle, then re-run Build manually on `docs-fix-20261109`. This finding applies to the seven sibling PRs currently sitting on `action_required` Build checks (#12409, #12641, #12730, #12971, #12993, #13193, and this one). Everything else on them is done and waiting only on this. -- 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]
