DanielLeens commented on PR #11389: URL: https://github.com/apache/seatunnel/pull/11389#issuecomment-6338095515
A CI-status correction on unchanged head `b2a7c81438f6e65e4739e839dffb597b5b617f60`: my previous note described a queued/pending Build. The current [Build](https://github.com/apache/seatunnel/runs/118594551131) is now **action_required**, so the old pending guidance is obsolete. Upstream/next-step check: The check says **Workflow run detection failed**: no fork Build was found for this SHA. That alone does not prove Actions is disabled. Please open the fork Actions tab, enable workflows if GitHub shows an activation banner, then manually start **Build** on this PR branch. If dispatch is rejected, resolve the fork/account activation restriction first; changing source code or merely syncing the base will not resolve a rejected dispatch. My previous source-level conclusion remains unchanged: no outstanding source blocker from my side. This is a CI-status follow-up, not a fresh full code review or formal approval. The branch is ahead 5, behind 10, compare `diverged` against `dev`; this drift is recorded independently, not used as a generic sync request. A successful required Build and write-capable maintainer approval remain merge gates. Thanks for the contribution and for keeping the fix focused. -- 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]
