davidzollo opened a new issue, #10688: URL: https://github.com/apache/seatunnel/issues/10688
## Background The scheduled `update_build_status.yml` workflow currently spends too much time syncing fork CI status back to upstream pull request checks. Its purpose is valid, but the current implementation does more work than necessary on every run. ## Current problems 1. It scans every open pull request on each schedule run, even when most PRs have had no recent activity. 2. It performs multiple nested REST API requests serially for each matching PR and check run, which creates avoidable N+1 latency. 3. It patches upstream check runs even when the status has already reached the same terminal state, which wastes API calls. ## Proposed improvement 1. Query only open PRs that were updated recently instead of paginating through the full open PR list. 2. Process PR synchronization tasks in bounded concurrent batches to reduce overall runtime without hitting secondary rate limits. 3. Compare the upstream check status with the fork workflow run result before issuing a patch request, and skip no-op updates. ## Expected result The workflow should keep the same external behavior for build status syncing, while significantly reducing scheduled runtime and GitHub API usage. -- 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]
