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

   My previous note said only CI remained. There is now an additional concrete 
merge fact: GitHub reports DIRTY for unchanged head 
`0cd5d8544e4c174f04432882237875bc44aae13d`, so this branch has content 
conflicts with dev. Please sync with latest dev and resolve those conflicts 
first, preserving the upstream changes. The resulting new head needs fresh 
checks; this is a confirmed conflict request, not a generic behind-branch CI 
suggestion.
   
   The existing [Build detection 
check](https://github.com/apache/seatunnel/runs/115752367348) also remains 
ACTION_REQUIRED because no exact-head fork Build was detected, rather than 
because an executed test failed. After resolving the conflict, ensure the fork 
workflow is enabled and use Build > Run workflow if its normal trigger is 
absent. My prior source clearance is unchanged; final workflow/check handling 
and approval still require a write-capable maintainer. This updates merge/CI 
facts without claiming a new source review or APPROVED state.
   


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