DanielLeens commented on PR #12051: URL: https://github.com/apache/seatunnel/pull/12051#issuecomment-5537865399
Thanks for digging further into this, @CryoThrust. I checked your fork's Actions history directly rather than just taking the check status at face value. You're right that Actions is genuinely enabled on `CryoThrust/seatunnel` — I can see other branches on your fork (your other `codex/seatunnel-*` branches) have real, completed `Build` workflow runs, so this isn't a repo-wide Actions-disabled problem like the usual first-time-contributor case. The specific issue is narrower: I searched the fork's full run history and there is no workflow run at all — not even a failed or cancelled one — for `codex/seatunnel-12045-test-lifecycle` at any commit, including the current head `70cfb3ff704d`. That matches what the apache-side check shows (`action_required` / "unable to detect the workflow run"): GitHub never received a `push` event for this branch that it turned into a run, so there's nothing for the required check to attach to. Since Actions is enabled and other branches on the same fork work fine, the lowest-cost fix here isn't a settings change — it's just getting one real `push` event onto this exact branch. I'd suggest: 1. Sync this branch with the latest `dev` (`git fetch upstream dev && git rebase upstream/dev`, or merge if you prefer to avoid a force-push) and push the result. A rebase is a legitimate, non-empty commit (not just a trigger no-op) and will also pick up any CI stabilization fixes that have landed on `dev` since this branch was created. 2. If that still doesn't produce a run, it's worth double-checking under your fork's Settings → Actions → General that "Allow all actions and reusable workflows" is selected specifically for this branch's workflow file version (not just the account-level toggle), since occasionally a fork-level Actions permission change doesn't retroactively apply to a ref that was pushed before the setting was flipped. Once a real `Build` run lands (pass or fail), ping me and I'll take another look — my code-side review already came back clean (see my previous comment), so this really is just the last procedural gate. -- 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]
