DanielLeens commented on PR #12875: URL: https://github.com/apache/seatunnel/pull/12875#issuecomment-6282873486
Thanks for digging into this, @hutiefang76, and for the precise check on the fork side. A few facts that may help narrow it down: - The Apache-side `Build` check for head `6b4777e7` is `action_required`, and it is only a pointer: it needs the real workflow run to exist in your fork. The 422 `Actions has been disabled for this repository` that you got when dispatching means the fork is not able to run workflows at all right now, so no push or rerun from the PR side will create a run. - Your fork did run `Build` before (the most recent run I can see is from 2026-10-08), so this looks like a state change on the fork or account rather than a repository configuration problem in this PR. - As a reviewer I cannot start or approve a run on the Apache side for a fork branch, and I cannot change fork settings, so I would not want to guess a workaround that skips the normal CI gate. Things worth checking on your side (I cannot see these from here, so this is a suggestion, not a diagnosis): 1. Open the `Actions` tab of your fork in the browser and see whether there is a banner asking to enable workflows; click it if present. 2. In the fork under `Settings > Actions > General`, confirm that actions are allowed, and check the account `Billing` page for any Actions usage limit or spending-limit message, because GitHub reports a blocked account like this with the same message. 3. After it is re-enabled, push an empty commit (or sync the branch with the latest `dev`, it is 8 commits behind now) so a fresh `pull_request` run is created. Your local run of the full JDBC suite (1,154 tests, 0 failures) plus the diff review is good evidence for the change itself, and my source-side conclusion remains: no blockers. A committer will still want the `Build` result before merge, so if the fork cannot be re-enabled, please say so here and the maintainers can decide how to proceed. -- 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]
