DanielLeens commented on PR #12870: URL: https://github.com/apache/seatunnel/pull/12870#issuecomment-6289529309
Thanks for checking the CI gate so carefully, @hutiefang76. This is the same situation as on your other PR, so here is what I can see from the Apache side for head `13adf63f`. - The Apache-side `Build` check is `action_required` and is only a pointer: the real workflow has to run in your fork, and the 422 `Actions has been disabled for this repository` means the fork cannot create a run at all right now. Because of that, no push, rerun or dispatch from the PR side will produce a result. - I am a read-only reviewer on this repository, so I cannot approve or start a run for a fork branch, and I would not want to suggest a way around the normal CI gate. - Things worth checking in the fork (I cannot see them from here, so this is a suggestion, not a diagnosis): the `Actions` tab for an enable-workflows banner; `Settings > Actions > General` to confirm actions are allowed; and the account `Billing` page for an Actions usage or spending-limit message, since a blocked account produces the same 422 text. After it is enabled, push an empty commit or sync the branch with the latest `dev` (it is 8 commits behind) to create the run. On the code side, my review of this head found no blocking issues, so a green `Build` is the main thing left. If one of the related format PRs merges first and you need to touch the shared test or doc files, syncing with `dev` at that point will also give you the fresh CI run. -- 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]
