DanielLeens commented on PR #12678: URL: https://github.com/apache/seatunnel/pull/12678#issuecomment-6310082808
Thanks for checking that so thoroughly, @kalayciburak, and sorry this is so frustrating. Your message tells me something useful: with Actions enabled and the `Build` workflow active, a `workflow_dispatch` request that still returns HTTP 422 "Actions has been disabled for this repository" means the block is not coming from the repository settings page. It is consistent with a restriction on the account or fork as a whole (for example a billing or spending-limit hold, or a flag GitHub has put on the fork), which only GitHub can lift. This is an inference from the error you quoted; I cannot see your account or fork state from here. Here is what I would try, in this order: 1. Open **Settings -> Billing and plans** on your account, and check the account notification banner and e-mail for a message about Actions being restricted. Clearing a hold usually restores Actions within minutes. 2. If nothing shows up, open a ticket with [GitHub Support](https://support.github.com/) quoting the exact 422 message and the fork `kalayciburak/seatunnel`; that response is a repository-level block that only their staff can remove. 3. If you would rather not wait, a fallback is to push the same branch to a fresh repository (or another account or organization you control) with Actions enabled, run `Build` there, and paste the run link here. Please do not open a duplicate PR for this unless a committer asks for it, so the review history stays in one place. There is no need to add an empty commit. The source side of this PR is unchanged since my last review, and the earlier head `dcd60585` was green in your fork, so what is still missing is one `Build` result on `03a99ef0`. The branch is now 1 commit behind `dev`; that does not block anything, and it can be synced after CI is available again. Once there is a green `Build` on the final head, I have nothing else to ask. Thanks again for the patience, and for a very clean fix! -- 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]
