DanielLeens commented on PR #13056:
URL: https://github.com/apache/seatunnel/pull/13056#issuecomment-6514196975

   The CI fact cited previously has changed: Build now reports ACTION_REQUIRED 
at workflow-run detection, with the explicit message that no fork Build was 
found for this head. This is not an executed PostgreSQL test failure and does 
not by itself prove Actions is disabled. Please open the fork Actions tab, 
enable workflows if disabled, and run the existing Build workflow on this PR 
branch; if an exact-head run already exists, link it for the aggregate 
maintainer instead of launching another. Current dev retains this fork-run 
adoption mechanism, so a simple sync alone cannot supply the missing run. The 
complete PostgreSQL type-identity and scalar/array integration/documentation 
blockers from my source review remain open.
   
   Snapshot 2026-10-30T03:23:54.080380+00:00: head 
`b86d39875619a306cc121faada82b5fb1abd8c62`; [Signal pull request 
update](https://github.com/apache/seatunnel/actions/runs/40874226519/job/123852266237)
 = `SUCCESS`; [Build](https://github.com/apache/seatunnel/runs/123861971366) = 
`ACTION_REQUIRED`.
   
   Base `dev`; comparison `diverged`, ahead 1, behind 3; merge state `blocked`. 
Behind/diverged alone is recorded metadata and does not add a sync request. 
This is an unchanged-head discussion/CI clarification, not a new complete 
source review, an effective approval or a dismissal of historical requested 
changes.


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