DanielLeens commented on PR #10257: URL: https://github.com/apache/seatunnel/pull/10257#issuecomment-6473967476
Thanks for the workflow reminder. My existing source conclusion on this unchanged head remains clear; the remaining CI issue is obtaining an actual exact-head fork Build and attaching its result. A missing run does not on its own prove that Actions is disabled, so check that setting and otherwise dispatch the existing Build workflow for this branch. There is no reason to add unrelated source changes or an empty commit merely to investigate that activation gate. Gate snapshot (2026-10-28T16:00:58+00:00), head `79d09069e051593c745feed5f6755ee47b0a3bc2`: [Build](https://github.com/apache/seatunnel/runs/122618167825) is `ACTION_REQUIRED`. The exact blocking stage is **Build workflow-run detection**: the check says no fork Build was found for this SHA. This is not an executed test failure and does not by itself prove that fork Actions is disabled. Open the fork Actions tab, enable workflows if needed, then manually run the existing Build workflow for this PR branch. If a matching run already exists, link it for a maintainer to reconcile the aggregate. No empty commit or speculative dependency change is requested. Upstream check: current dev retains the fork-run adoption workflow and its scheduled/manual status-refresh path. A base sync alone cannot enable fork Actions or supply a missing exact-head workflow run, so I am not prescribing sync as the fix for this activation gate. My [previous source conclusion](https://github.com/apache/seatunnel/pull/10257#pullrequestreview-5651228525) remains clear for the reviewed scope. CI is not being passed by inference, and this follow-up is not an effective approval. Comparison recorded in this scan: base `dev`, `diverged`, ahead 11 / behind 48, no merge conflict. Branch drift is metadata here and is not an additional sync request. -- 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]
