DanielLeens commented on PR #12853: URL: https://github.com/apache/seatunnel/pull/12853#issuecomment-6457412410
Thanks for rechecking the fork settings. If Actions is enabled in the UI and a manual dispatch still returns `HTTP 422: Actions has been disabled for this repository`, the restriction is almost certainly applied above the repository level (account-level or billing/spending-limit state, or a GitHub-side restriction on that fork), so a committer cannot enable it from the Apache side, and the required `Build` check cannot attach to this head without a real run in your fork. The lowest-cost next steps, in order: 1. Check Settings -> Billing and plans (and the account notices) for any hold or restriction, and contact GitHub Support if the fork shows as restricted. 2. If that is not quickly fixable, create a fresh fork (or a new repository fork under the same account), enable Actions there, push the same branch (the tree on `11a1c7df` already matches the head that passed the fork CI earlier), and open a new PR from it, referencing this one. We can then close this PR as superseded once the new one is green. The source side has no blocker from my review, so no code change is needed for either route. If either step fails, please paste the exact error here and I will help narrow it down. -- 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]
