preko-p commented on PR #11002: URL: https://github.com/apache/seatunnel/pull/11002#issuecomment-4658138509
I retried the fork-side unblock steps and the source branch is now on current `dev`. What I did: - rebased on current `dev` and force-pushed the PR branch - verified fork Actions permissions: enabled, `allowed_actions: all` - pushed an empty trigger commit (`9d16dd2`) after the rebase That did trigger fresh Apache-side checks (`Notify test workflow` and `labeler` both passed), but the `Build` check still ends with `Workflow run detection failed`. One odd detail: the fork Actions API currently reports zero registered workflows for `preko-p/seatunnel`, even though the workflow files are present in the fork. I do not see a source-code change left to make on the PR branch itself. Could a maintainer trigger/approve the workflow from the upstream side, or advise what else you want me to do for the fork workflow registration? -- 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]
