DanielLeens commented on PR #13061: URL: https://github.com/apache/seatunnel/pull/13061#issuecomment-6503353103
The fork discovery check now establishes a successful Build on this exact head (40897010419), while the PR aggregate has not yet adopted a runtime Build. My source conclusion remains clear. Please have a maintainer reconcile the existing matching run and the final effective approval gate; do not rerun blindly or add a source commit solely to refresh that pointer. This is additional CI evidence, not a claim of local Lance/JNI execution. Checked 2026-10-29T17:10:40+00:00; head `c91e4babfb4048c79b274501a63a65dd82f071cf`. [Signal pull request update](https://github.com/apache/seatunnel/actions/runs/40906473200/job/123562495878) = `QUEUED` Verified matching fork evidence: [Build run 40897010419](https://github.com/SEPURI-SAI-KRISHNA/seatunnel/actions/runs/40897010419), attempt 1, `success`. Repository aggregate/adoption and effective approval remain separately evaluated. Comparison: base `dev`, head `c91e4babfb4048c79b274501a63a65dd82f071cf`, `ahead`, ahead 1 / behind 0; 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]
