From dc937e63a17c0b5cd52c217026df47235db3678a Mon Sep 17 00:00:00 2001 From: scanner <280983584+hivecommons-hive[bot]@users.noreply.github.com> Date: Fri, 6 Nov 2026 12:14:46 -0500 Subject: [PATCH] docs: note PR-target re-triggers queue behind the in-flight native-queue-policy run Signed-off-by: scanner <280983584+hivecommons-hive[bot]@users.noreply.github.com> --- src/docs/native-merge-queue.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/src/docs/native-merge-queue.md b/src/docs/native-merge-queue.md index 17fda3c58f..b21f83ad93 100644 --- a/src/docs/native-merge-queue.md +++ b/src/docs/native-merge-queue.md @@ -215,6 +215,10 @@ metadata, not a fabricated last-member PR event. - On `pull_request_target`, it executes only the trusted base's validator and waits up to 22.5 minutes for the five existing policy checks on that exact PR head. No candidate code is executed; tokens are read-only. + Label, edit, or unlabel events re-trigger this workflow and serialize behind + any in-flight run (the concurrency group is per-PR and never cancels + in-progress); the queued run re-reads mutable PR state after the prior run + finishes, preserving fail-closed semantics. - On a group it executes the event's trusted `base_sha` validator. It reads the live queue prefix ending at the event's exact synthetic head, verifies contiguous membership and the base/head commit chain, and checks