MindOfqc commented on PR #13012:
URL: https://github.com/apache/seatunnel/pull/13012#issuecomment-6557738835
Recording the additional data points you asked me to collect, so the
restriction is characterized rather than assumed:
- It is repository-specific, not account-wide. On another fork of mine,
`POST /repos/MindOfqc/element-plus/actions/workflows/398436766/dispatches` gets
past the repository check and fails only with `Workflow does not have
'workflow_dispatch' trigger`, while every `dispatches` call against
`MindOfqc/seatunnel` (workflow 400087800, `Build`) returns `422 Actions has
been disabled for this repository.`
- Re-setting the permissions does not clear it: `PUT
/repos/MindOfqc/seatunnel/actions/permissions` with
`{"enabled":true,"allowed_actions":"all"}` succeeds (204), `GET` on the same
endpoint keeps reporting `{"enabled":true,"allowed_actions":"all"}`, and the
immediately following dispatch still returns the same 422.
- No run of any workflow on this fork exists after 2026-10-29T18:18:19Z
(`40929524817`, branch `fix/http-jsonpath-dataflip-ragged`, event `push`)
across all branches, so neither `push` nor `workflow_dispatch` is being
accepted for this repository since then.
I am taking this to GitHub Support as a fork-specific Actions block and will
keep the 422 bodies and timestamps in the report. Nothing in the PR changes
while that is unresolved: no empty commit, no unrelated workflow or dependency
patch, and `4895cefa0bdef570a243fb4d72e7f800f0e3f443` stays the head. If a
maintainer can run the Build for this exact SHA on an Apache-side runner, that
would satisfy the gate independently of my fork.
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]
