DanielLeens commented on PR #12511: URL: https://github.com/apache/seatunnel/pull/12511#issuecomment-6503417988
Thanks @SEZ9 for closing the coverage discussion. I agree with the existing source clearance for this unchanged head and the named cancel/non-cancel restore tests; #12623 remains a separate dependent contribution. The remaining action is effective maintainer approval/branch protection. Being diverged without conflicts does not require a contributor rebase or another source change here. Checked 2026-10-29T17:13:40+00:00; head `a691fb195d32381b3a43560eba4586861366a6d8`. [Notify test workflow](https://github.com/apache/seatunnel/actions/runs/37216100246/job/111476805914) = `SUCCESS`; [labeler](https://github.com/apache/seatunnel/actions/runs/37216100242/job/111476806239) = `SUCCESS`; [Build](https://github.com/apache/seatunnel/runs/111623841460) = `SUCCESS` Comparison: base `dev`, head `a691fb195d32381b3a43560eba4586861366a6d8`, `diverged`, ahead 4 / behind 249; GitHub mergeable state `unstable`. 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]
