Repository navigation
ci: add the merge-queue removal label workflow - #2056
Merged
Merged
Conversation
github-merge-queue
Bot
removed this pull request from the merge queue due to failed status checks
Nov 15, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds the Ground Control
Merge Queue Removedworkflow. When thedevmerge queue removes an open pull request without a merge, the workflow adds themerge-queue-removedlabel. It removes the label when the pull request enters the queue again or closes. The action policy rejects a write token on apull_requestjob, so this change adds a reviewed boundary that admitspull-requests: writeonly for this exact job shape.Requirement UIDs
Related Issues
Closes #2052
ADR Impact
Changes
.github/workflows/merge-queue-removed.ymlfrom Ground Control. The job holds onlypull-requests: write. Anissues: writetoken got HTTP 403 when it added the label._queue_label_boundarytotools/tooling_artifact_policy_actions.py. It admitspull-requestswrite only for thelabeljob in this workflow, with queue events only, nousesstep, no container, no secret, and theubuntu-latestrunner.test_release_workflows.py.test_issue_2052_merge_queue_label.pyfor the workflow shape and the boundary limits.test_completed_replacement_publishes_accounting_and_exact_scientific_versionsexplicit 10000 ms supervision budgets. Its study validation reads 16 runs in one observation call, which went over the 2000 ms default on a loaded merge-group runner.docs/DEVELOPMENT_WORKFLOW.md.Test Plan
Targeted: test_issue_2052_merge_queue_label.py, test_issue_1313_workflow_policy.py, test_issue_2026_merge_queue.py, the two changed tests in test_release_workflows.py, and the changed test in test_issue_1630_record_recovery.py. A 50 ms observation budget reproduced the merge-group failure exactly.
Ground Control Checks
Traceability
Checklist
Documentation
Updated: see diff.