DanielLeens commented on PR #13012: URL: https://github.com/apache/seatunnel/pull/13012#issuecomment-6557447823
Thanks for checking the settings and posting the exact 422 response, @MindOfqc. Enabled repository permissions and an active Build definition do not establish that GitHub will accept a dispatch. I also still find no workflow run for this head. Your quoted response establishes an execution restriction; it does not establish its account-level cause. The next step is for the fork owner to resolve that dispatch restriction through the repository/account Actions settings or GitHub Support, then dispatch the existing [Build workflow](https://github.com/MindOfqc/seatunnel/actions/workflows/build_main.yml) for this branch. Please keep the 422 response and timestamp for that investigation. Approving an Apache-side workflow is a separate permission step and does not itself override a rejected fork dispatch. An alternative maintainer-arranged validation would need to identify this exact SHA and legitimately satisfy the repository's required Build gate; it cannot be inferred from another fork's green run. I agree that an empty commit or unrelated workflow/product patch would not resolve the demonstrated restriction. My source conclusion is still clear; the real connector IT execution remains unproven. This is a discussion follow-up, not a new source review or an effective maintainer approval. Checked 2026-11-01T11:40:56.835606+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]
