DanielLeens commented on PR #11077: URL: https://github.com/apache/seatunnel/pull/11077#issuecomment-6503453022
Thanks @SEZ9 for the focused checklist. The unchanged head still has the source/documentation and contract-coverage requests from my published conclusion; I am not confirming unpushed fixes or issuing a second full review. GitHub also reports a real conflict with dev, so please sync and resolve that conflict while preserving both intended changes, then provide the resulting head for complete re-review. The missing exact-head fork Build is a separate gate: start/link the existing workflow without an empty trigger commit. Neither CI activation nor conflict resolution alone clears the remaining source requests. Checked 2026-10-29T17:15:15+00:00; head `8b383c04eeed65c41a14ba756100a33f430124eb`. [Notify test workflow](https://github.com/apache/seatunnel/actions/runs/38302185787/job/114987521192) = `SUCCESS`; [labeler](https://github.com/apache/seatunnel/actions/runs/38302185861/job/114987522576) = `SUCCESS`; [Build](https://github.com/apache/seatunnel/runs/114987916217) = `ACTION_REQUIRED` Comparison: base `dev`, head `8b383c04eeed65c41a14ba756100a33f430124eb`, `diverged`, ahead 38 / behind 168; GitHub mergeable state `dirty`. GitHub reports real merge conflicts; the author must sync the latest base and resolve them before the resulting head can be checked and re-reviewed. 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]
