DanielLeens commented on PR #12871: URL: https://github.com/apache/seatunnel/pull/12871#issuecomment-6397832951
Thanks for the contribution. GitHub now reports **DIRTY / merge conflicts** for unchanged head `76852b68c9d19db4991fee969fd2b4e84952c141`, superseding my earlier conflict-free merge statement. The Apache [Build check](https://github.com/apache/seatunnel/runs/120693769773) still reports in progress and points to [fork run 39778817466](https://github.com/hutiefang76/seatunnel/actions/runs/39778817466). The connected API returned only one page of jobs, so I am not calling the full fork matrix green or complete. Please sync latest dev and resolve the reported conflicts while preserving both upstream and this PR's DECIMAL compatibility notes; then let CI run on the resulting head. This is a conflict-resolution action, not a claim that branch drift caused a test failure. The source-level findings from my last full review remain clear. A complete successful current-head Build and write-capable maintainer approval remain separate gates. Live comparison recorded in this batch: base dev, `diverged`, ahead 5 / behind 25. Daniel has READ permission; this is a technical follow-up, not an effective approval. No second source review is being issued on the unchanged head. -- 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]
