SiriusTL666 commented on PR #12974:
URL: https://github.com/apache/seatunnel/pull/12974#issuecomment-6409066349

   Thank you — and thanks for checking the fork run yourself rather than taking 
my report on trust.
   
   **On the missing Apache-side Build check, I dug into it, and the cause is 
not a delay.**
   
   On this head, `apache/seatunnel` does have three check suites registered, 
but all of them are stuck at `action_required`:
   
   | Item | State at `fcac22db` |
   |---|---|
   | Apache-side check suites | 3, all `action_required` |
   | Apache-side workflow runs | only `PR signal`, `action_required` |
   | Combined commit status | `pending`, 0 statuses |
   | Fork-side Build | `completed / success` |
   
   So the Build job is not missing — it is **gated**. GitHub holds the 
`pull_request` workflows for first-time contributors until someone with write 
access approves them. Re-dispatching the workflow on the branch would not help 
either, because `workflow_dispatch` for that workflow resolves against my fork 
(where I can run it) and I have no permission to dispatch in `apache/seatunnel`.
   
   This is the same gate that blocks the other PRs I have open. My 
understanding is that only a write-capable maintainer approving the runs (or 
merging, which makes the question moot) can clear it.
   
   **What is verified, for the record:** Build `40204876571` on `fcac22db` — 
completed, success — covering the four unit-test lanes (JDK 11/17 × 
Ubuntu/Windows), the two updated-modules integration jobs, License header, Code 
style, Dead links and Sanity check. The skipped suites are module-filtered, and 
I am not counting them either.
   
   So I read the state as: no source-level blocker from you, CI verified in the 
fork, and the remaining gate is the write-access approval. Nothing else needed 
from me unless you would like the approval itself escalated to someone who can 
grant it.


-- 
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]

Reply via email to