Yicong-Huang opened a new pull request, #4672:
URL: https://github.com/apache/texera/pull/4672

   ## What changes were proposed in this PR?
   
   Adds a small GitHub Actions workflow (`.github/workflows/auto-queue.yml`) 
that runs after every push to `main`. It scans open PRs targeting `main` that 
have auto-merge enabled, picks the oldest one whose head is behind `main` (and 
not conflicting/draft), and calls `updateBranch` on it — i.e., merges `main` 
into the PR head so its required CI re-runs and auto-merge can fire.
   
   Picks one PR per main push, serialized via a `concurrency` group, so the 
queue advances at most one step per merge.
   
   ## Any related issues, documentation, discussions?
   
   Refs #4553. This is a temporary stand-in while we wait on the INFRA ticket 
to enable native GitHub Merge Queue. The workflow should be deleted once Merge 
Queue is available on `apache/texera`.
   
   ### Token requirement
   
   The default `GITHUB_TOKEN`'s push to a PR head does **not** retrigger 
required workflows on that PR. To make auto-merge actually fire, set a 
fine-grained PAT (Contents: write, Pull requests: write, Metadata: read) as the 
repo secret `AUTO_MERGE_TOKEN`. The workflow falls back to `GITHUB_TOKEN` if 
the secret is absent (useful for dry-running).
   
   ## How was this PR tested?
   
   Not yet — workflow runs only when on `main`. Plan:
   
   - [ ] Land this PR.
   - [ ] Configure `AUTO_MERGE_TOKEN` repo secret.
   - [ ] Verify on the next merge-to-main that the workflow logs identify a 
candidate PR (or "No auto-merge PRs need updating") and that the chosen PR's 
branch gets updated.
   
   Manual sanity-check: `workflow_dispatch` is enabled so it can be invoked 
from the Actions tab without a real 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]

Reply via email to