Yicong-Huang opened a new pull request, #4678: URL: https://github.com/apache/texera/pull/4678
## What changes were proposed in this PR? In \`.github/workflows/auto-queue.yml\`, replace the \`mergeStateStatus === 'BEHIND'\` filter with an iteration over eligible auto-merge PRs (non-draft, non-conflicting). For each candidate, call \`updateBranch\`; on failure (already up-to-date / merge conflict / etc.), warn and try the next. Stop at the first PR that actually got updated. ## Any related issues, documentation, discussions? Follow-up to #4672. Observed in [run 25248773692](https://github.com/apache/texera/actions/runs/25248773692/job/74037400879): the workflow fired ~3s after a push to main, when GitHub had not yet recomputed \`mergeStateStatus\` for open PRs. PR #4652 (\`mergeable=MERGEABLE\`, \`autoMergeRequest != null\`) was a real candidate but its \`mergeStateStatus\` was \`UNKNOWN\` at query time, so the strict \`=== 'BEHIND'\` filter dropped it and the run logged "No auto-merge PRs need updating". \`mergeStateStatus\` is documented as computed asynchronously, and there's no reliable bound on how long it stays \`UNKNOWN\` after a base-branch push. Letting \`updateBranch\` decide whether there's actual work to do is more robust than depending on a flaky pre-flight signal. ## How was this PR tested? Not yet — workflow runs only on push-to-main. Will observe behavior on the next merge. ## Was this PR authored or co-authored using generative AI tooling? Generated-by: Claude Opus 4.7 (Claude Code) -- 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]
