DanielLeens commented on PR #12572: URL: https://github.com/apache/seatunnel/pull/12572#issuecomment-6210075083
Thanks @nzw921rx for the ping, and @Nikk8091 for the detailed notes on the fork side. Status as of head `ed4b9bc085ff` (unchanged since my last review): no code, test, docs or compatibility blockers on my side, and CI is the only remaining item. The apache-side `Build` check is still `action_required` and no workflow run exists for this SHA, because the fork runs the real jobs and Actions is disabled in `Nikk8091/seatunnel`. The branch is 2 ahead / 28 behind `dev` with no conflict, so there is no need to rebase just for this. Concrete next steps for @Nikk8091. I cannot see your fork settings, so these are the usual causes of the 422 "Actions has been disabled for this repository": 1. In the fork, open `Settings -> Actions -> General` and set "Actions permissions" to "Allow all actions and reusable workflows". Re-enabling only the single workflow in the Actions tab is not enough when the repository-level setting is off. 2. Open the fork's `Actions` tab and, if you see the banner "Workflows aren't being run on this forked repository", click "I understand my workflows, go ahead and enable them". 3. Push a new commit to the PR branch (an empty one is fine, `git commit --allow-empty -m "Trigger CI"`). Enabling Actions does not retroactively create a run for an already-pushed SHA, and `workflow_dispatch` of `build_main.yml` on an arbitrary branch is not what the PR check reads, so a fresh push is what creates the run that the PR `Build` check follows. 4. If step 1 is greyed out or reverts, the setting is probably controlled by an account or organization policy; in that case please tell us here and a committer can suggest an alternative. Once the new run is green on the new head, I will update my review to approve, since CI was the only blocker. Thanks for the patience, and thanks @nzw921rx for flagging it. -- 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]
