DanielLeens commented on PR #11627: URL: https://github.com/apache/seatunnel/pull/11627#issuecomment-6557314320
Thanks again. A CI gate completed after my previous discussion reply: the current-head Build now reports ACTION_REQUIRED, with the exact stage “Workflow run detection failed”. The [check](https://github.com/apache/seatunnel/runs/121485488185) says no matching Build run was detected for this SHA. That is a workflow-discovery gate, not an executed OSS test failure and not, by itself, proof that Actions is disabled. Please make the normal Build run for this exact branch/head available, or link an existing matching run for adoption by the repository's scheduled/manual status workflow. Do not add unrelated product changes or an empty commit merely to investigate a missing aggregate. The latest dev retains the existing fork-run adoption mechanism; syncing alone cannot supply an absent execution. The previously recorded DEBUG credential-logging, documentation and live OSS validation requests remain open independently. This message does not confirm live OSS acceptance, clear those requests or issue approval. Checked 2026-11-01T11:27:22.579124+00:00; unchanged head `4c4330c114d651e199b1dbc5ca58391b43498ab3`. Current checks: [Build](https://github.com/apache/seatunnel/runs/121485488185)=ACTION_REQUIRED. Base `dev`, compare `diverged`, ahead 3 / behind 76; merge `UNKNOWN` / `REVIEW_REQUIRED`. Drift is recorded independently; it does not itself request synchronization. Daniel has READ permission. This is a CI/merge-gate clarification, not another full source review, effective approval or dismissal. -- 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]
