MindOfqc commented on PR #13020:
URL: https://github.com/apache/seatunnel/pull/13020#issuecomment-6633445532

   Thanks for the re-review and for confirming that no source/test/docs item 
remains. Answering the single open item (CI) with the state as of now.
   
   **Checks on head `10b2a9752b`**
   
   | Check | Status |
   |---|---|
   | `Signal pull request update` | completed / success 
([41666242607](https://github.com/apache/seatunnel/actions/runs/41666242607)) |
   | `Build` | completed / **action_required** — no run has executed for this 
SHA |
   | `Label-when-reviewed` | completed / action_required 
([41730198272](https://github.com/apache/seatunnel/actions/runs/41730198272)) |
   
   **Fork side: the documented hand-start path is refused by GitHub**
   
   `build_main.yml` on this branch carries the `workflow_dispatch` trigger 
added exactly for this situation, so I tried to start `Build` for 
`fix/http-jsonpath-dataflip-ragged` from the API:
   
   ```
   POST /repos/MindOfqc/seatunnel/actions/workflows/400087800/dispatches  
ref=fix/http-jsonpath-dataflip-ragged
   → 422 {"message":"Actions has been disabled for this 
repository.","status":"422"}
   ```
   
   while the read-only endpoint for the same repository still reports the 
opposite:
   
   ```
   GET /repos/MindOfqc/seatunnel/actions/permissions
   → {"allowed_actions":"all","enabled":true,"sha_pinning_required":false}
   ```
   
   The newest fork run GitHub accepted is still `40929524817` (older head 
`aa48ae2fc9`, 2026-10-29T18:18:19Z); nothing has been accepted since for any 
branch or head. The restriction is on the write path only, which is why the 
permissions GET looks healthy — and it is not something the branch can work 
around. Following your note, no empty commit and no code change is being pushed.
   
   What unblocks this head: a maintainer approving the pending run so `Build` 
executes for `10b2a9752b`, or a committer triggering a Build for that exact 
SHA. Reporting the GET/POST contradiction to GitHub Support has to come from 
the account owner, so it is prepared but not filed from here. I will post the 
run link on this PR as soon as a Build executes for this head; until then 
`CI_NOT_ENABLED` is accurate and nothing else is outstanding — the source, 
tests and en/zh docs are exactly as reviewed.
   
   Prepared with an AI coding agent.
   


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