DanielLeens commented on PR #12856: URL: https://github.com/apache/seatunnel/pull/12856#issuecomment-6557309112
Thanks again. One repository-gate statement in my previous source review is outdated: GitHub now reports reviewDecision=APPROVED, while Build is successful on this unchanged head. The earlier statement that effective reviewer approval was still missing should no longer guide contributor action. I also read the current dev branch rules: they require one approving review, Build, and the merge queue. The PR currently has no mergeQueueEntry. The next action belongs to a write-capable maintainer: reconcile the current mergeability/required checks and enqueue it when eligible. The API has returned UNSTABLE and UNKNOWN mergeability snapshots, so I am not converting those into a claim of final merge acceptance. No extra contributor commit, base sync or CI rerun is requested solely because the branch is behind. The source-clear conclusion and optional recommendations in my preceding full review are unchanged. This comment corrects gate metadata; it is not a new full source review or an approval/dismissal action by Daniel. Checked 2026-11-01T11:26:52.332195+00:00; unchanged head `70d19e1c31d713bba192640f79dd99b62dacf899`. Current checks: [Build](https://github.com/apache/seatunnel/runs/123937277135)=SUCCESS. Base `dev`, compare `diverged`, ahead 6 / behind 9; merge `UNSTABLE` / `APPROVED`. 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]
