DanielLeens commented on PR #13020: URL: https://github.com/apache/seatunnel/pull/13020#issuecomment-6503375638
Thanks @rwzdk for enabling Actions and reporting both attempts. I verified the unchanged head and the successful second fork Build, so my earlier missing-workflow guidance is withdrawn. The earlier factory-reachable scenario and full padded-row assertions (Issues 1 and 2 in the source review) remain required; a recovered checkpoint-test lane does not close those independent requests. No empty commit or unrelated checkpoint patch is needed. Checked 2026-10-29T17:11:43+00:00; head `c6ea0b075f928e0710819ceda7deebe70e33ab2a`. [Signal pull request update](https://github.com/apache/seatunnel/actions/runs/40547326600/job/122618104416) = `SUCCESS`; [Build](https://github.com/apache/seatunnel/runs/123244893853) = `SUCCESS` Comparison: base `dev`, head `c6ea0b075f928e0710819ceda7deebe70e33ab2a`, `diverged`, ahead 1 / behind 26; GitHub mergeable state `blocked`. Behind/diverged alone is recorded metadata and does not add a sync request. Daniel has READ repository permission. This is a discussion/CI clarification, not a new complete source review, an effective APPROVED event or dismissal of historical requested changes. A write-capable maintainer must perform any required final approval/dismissal. Thanks for keeping the follow-up 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]
