Repository navigation
π Accept pull_request in v6 native-queue-policy script - #19115
clubanderson wants to merge 2 commits into
Conversation
Refs #19100 Signed-off-by: Andy Anderson <andy@clubanderson.com>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Open PR overlap checkβ
Resolved: no conflicting open PRs or same-file overlaps remain against |
Signed-off-by: Andy Anderson <andy@clubanderson.com>
|
Hive status β updated in place; edits do not notify. Full history is in the Activity Monitor. @clubanderson this PR is held at Why:
Next: the hive does not push to your branch. Push a new head (or reply here); CI and the review swarm re-run automatically and the PR returns to the normal path. |
|
Superseded: #19100 merged into v6 carrying v5's full native-queue-policy script, which already accepts pull_request. Nothing left to port. |
The v5 to v6 top-up PR #19100 fails
native-queue-policywithUnhandled error: Error: Unsupported policy event.Cause: v5 moved
native-queue-policy.ymlfrompull_request_targetto plainpull_request(GitHub blockspull_request_targetby default on public repos from 2026-12-02). The workflow checks out the trusted base ref to run the script, and for PRs into v6 that is v6's script, which only acceptspull_request_target. The top-up brings the new workflow but the base script cannot be updated by it: a chicken-and-egg.Fix: port only v5's event acceptance (
PR_EVENTS, used for the PR-event branch, the cosmetic label flip check and the policy check source).pull_request_targetstays accepted. The workflow file is untouched; the top-up supplies it. Tests cover both events.Refs #19100
π€ Generated with Claude Code