Yicong-Huang opened a new pull request, #4849:
URL: https://github.com/apache/texera/pull/4849
### What changes were proposed in this PR?
Add an `emergency` label fast-path to the Auto Queue.
A PR carrying the `emergency` label is now bumped before any non-emergency
PR regardless of CREATED_AT, and its presence in `BEHIND` bypasses the
in-flight guard so a non-emergency PR's running CI does not delay the bump.
Within each priority class (emergency / normal) GraphQL's CREATED_AT-ASC order
is preserved, so ordering among peers is unchanged.
Eligibility gates still apply unchanged — `emergency` prioritizes the bump,
it does **not** bypass review:
- auto-merge enabled
- not a draft
- not conflicting
- `reviewDecision=APPROVED`
- zero unresolved review threads
The GraphQL query gains `labels(first: 20) { nodes { name } }`. The label
name in the workflow is `emergency` (constant `EMERGENCY_LABEL`); change one
line if a different label is preferred.
Logs grow a `[emergency]` tag on the per-PR classify line and the `→
updateBranch` line, plus an explicit "bypassing in-flight guard" message when
the bypass kicks in.
### Any related issues, documentation, discussions?
Builds on #4672 (initial workflow), #4678 (UNKNOWN retry + eligibility
gates), and #4845 (extra triggers + in-flight guard).
### How was this PR tested?
`yaml.safe_load` parses the workflow. `node --check` (wrapped in `async
function`) parses the script body. A standalone unit test on the priority logic
confirms ordering: given `[#100 docs, #101 emergency, #102 plain, #103
emergency+fix]`, the bump order is `[101, 103, 100, 102]`.
### Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Opus 4.7, 1M context)
--
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]
