DanielLeens commented on PR #12169: URL: https://github.com/apache/seatunnel/pull/12169#issuecomment-6473567152
Thanks for the conflict follow-up. The latest GitHub conflict state below supersedes earlier mergeable snapshots; a prior merge of dev does not guarantee that the branch stays conflict-free as dev advances. Separately, my existing Issue 1 still requires restoring the strict tag-mismatch assertion. Even with green CI, that test-strictness request is not cleared by an unchanged head or another reviewer's conflict-only acknowledgment. Gate snapshot (2026-10-28T15:44:49+00:00), head `ff9c68fe4e92559606f4b5f794f51f531624a752`: [Build](https://github.com/apache/seatunnel/runs/121537071208) is `SUCCESS`. The green check does not clear the independent source/documentation or scope requests in my [previous conclusion](https://github.com/apache/seatunnel/pull/12169#pullrequestreview-5646775957). Those requests remain unchanged; this is not an approval. Separately, GitHub reports merge conflicts with `dev`. Please sync the latest base and resolve the conflicts first; the resulting new head needs checks and re-review. This conflict gate is independent of CI and existing source findings. -- 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]
