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

   Thanks for summarizing the plan, @SEZ9 — that matches what I outlined above.
   
   Quick status check on the current head (`942d656463d5`): the branch is still 
`diverged` from `dev` (`mergeStateStatus: DIRTY`, GitHub reports `CONFLICTING`) 
and the `Build` check is still failing, so both items are still open:
   
   1. Rebase onto the latest `dev` and resolve the doc/test conflicts.
   2. Address the restore-path review items from my earlier comment, then push 
an updated commit.
   
   Once an updated commit lands I'll do a full re-review of the restore path 
against the new head. Happy to help narrow down the CI failure further if it's 
not resolved by the rebase alone — just share the new failing check link.


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