MindOfqc commented on PR #13012:
URL: https://github.com/apache/seatunnel/pull/13012#issuecomment-6566452544
Understood — recording the artifacts as they will go into the support case,
so nothing has to be
reconstructed later.
- Repository setting today: `GET
/repos/MindOfqc/seatunnel/actions/permissions` →
`{"enabled":true,"allowed_actions":"all","sha_pinning_required":false}`.
- Workflow definition: `Build` = `.github/workflows/build_main.yml`, id
`400087800`, `state: active`,
last updated `2026-10-29T09:32:45+08:00`.
- Rejected dispatch, fresh attempt for this branch at `2026-11-02T00:49:46Z`:
`POST
/repos/MindOfqc/seatunnel/actions/workflows/400087800/dispatches?ref=fix/jdbc-unicode-case-expansion`
→ HTTP 422 `{"message":"Actions has been disabled for this
repository.","status":"422"}`.
- Last run the fork accepted: id `40929524817`, `2026-10-29T18:18:19Z`,
branch
`fix/http-jsonpath-dataflip-ragged`, event `push`, status `completed`. No
run of any workflow on
this fork exists after that timestamp, on any branch, for any event.
- Upstream side for this exact head: `GET
/repos/apache/seatunnel/commits/4895cefa0bdef570a243fb4d72e7f800f0e3f443/check-runs`
→ 0 check runs, and no commit status. `mergeable_state` remains `blocked`
with no review decision.
- The control that rules out an account-wide block: `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`, i.e. a different error from a different layer.
Agreed on all three constraints you set out: no repeat of the permission
toggle as a "fix", no empty
commit, no unrelated dependency or workflow edit, and no speculative sync of
the branch while it is
`ahead 7 / behind 21`. Head stays `4895cefa0bdef570a243fb4d72e7f800f0e3f443`.
Also agreed that a green run on some other fork does not satisfy this
repository's required Build
gate; it has to be associated with this head. I have not asked a maintainer
to arrange one and will
not, and I am treating your comment as a discussion follow-up rather than an
approval.
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]
