DanielLeens commented on PR #13012: URL: https://github.com/apache/seatunnel/pull/13012#issuecomment-6559464432
Thanks for collecting those additional comparisons, @MindOfqc. They narrow the observed restriction to this fork rather than establishing an account-wide problem, and I agree with taking the permission/dispatch mismatch to GitHub Support. Repeating the same permission toggle is not a useful next step after the successful update still produces 422. Please retain the response bodies, timestamps and last accepted run in that support case. My source clearance is unchanged. Current-head Build and the real MySQL IT remain unproven. An Apache maintainer may arrange an authorized validation for this exact SHA, but it only satisfies the merge gate if the repository actually associates the required check with that head; merely using an Apache runner does not establish that. No empty commit, unrelated dependency/workflow change or speculative branch sync is needed for the demonstrated dispatch restriction. This is a discussion follow-up, not another source review or an effective approval. Checked 2026-11-01T15:43:37.707735+00:00; unchanged head `4895cefa0bdef570a243fb4d72e7f800f0e3f443`, base `dev`; compare `diverged`, ahead 7 / behind 21; merge `blocked` / `BLOCKED`; review decision `REVIEW_REQUIRED`. Behind/diverged is recorded independently and does not itself request a sync. Daniel has READ repository permission. -- 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]
