DanielLeens commented on PR #12101: URL: https://github.com/apache/seatunnel/pull/12101#issuecomment-6503428505
Thanks @SEZ9. My source-level clearance is unchanged. The current aggregate still reports the exact-head fork Build discovery gate, rather than an executed source-test failure. Please use the fork Actions tab to enable workflows if disabled and start the existing Build for this branch, or provide an already-existing matching run for maintainer reconciliation. No empty commit, dependency edit or drift-only rebase is needed. Historical requested changes and the eventual effective approval/dismissal still belong to a write-capable maintainer. Checked 2026-10-29T17:14:09+00:00; head `55831abaef1e1aac58988977c1da8e73a27d9417`. [Signal pull request update](https://github.com/apache/seatunnel/actions/runs/40168278125/job/121480735658) = `SUCCESS`; [Build](https://github.com/apache/seatunnel/runs/121486172557) = `ACTION_REQUIRED` Comparison: base `dev`, head `55831abaef1e1aac58988977c1da8e73a27d9417`, `diverged`, ahead 6 / behind 58; 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]
