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

   Thanks for the re-review. Confirming where this stands so the record is 
complete.
   
   No source change is requested and none was made: head stays
   `4d98b290adad5002d941f62203c34329afd4b5a8`. The padding contract, the 
factory-routed
   regression case, the exact matrices, the option spelling and the paired 
en/zh docs notes are all
   already in the branch, and your report records no remaining source finding 
against this head.
   
   Re-checked the execution gate today rather than relying on the earlier 
snapshot:
   
   - `POST /repos/MindOfqc/seatunnel/actions/workflows/400087800/dispatches` at
     `2026-11-02T00:49:46Z` still returns HTTP 422
     `{"message":"Actions has been disabled for this 
repository.","status":"422"}`
   - while `GET` on the same repository reports 
`{"enabled":true,"allowed_actions":"all"}` and the
     `Build` workflow (`build_main.yml`) is `active`.
   - the last run accepted on the fork at all is `40929524817`, 
`2026-10-29T18:18:19Z`, branch
     `fix/http-jsonpath-dataflip-ragged`. Nothing has been created since, for 
any branch or any event.
   - `GET /repos/apache/seatunnel/commits/4d98b290.../check-runs` returns 0 
check runs and no commit
     status.
   
   So this is the fork-specific dispatch restriction characterised on the 
sibling PR, not a repository
   toggle I can flip and not something a rebase or an unrelated edit would 
cure. It is going to GitHub
   Support with the 422 bodies, the timestamps and that last accepted run 
attached. I am not adding an
   empty commit to force a `push` event, and I am not touching scheduled 
workflows or dependencies.
   
   That leaves the exact-head Build genuinely unproven from my side. If someone 
with write access can
   run it for this SHA, I will report the result here. I am not asking for that 
as an action item.
   
   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