ci: add workflow to block merging PRs with "status: blocked" label - #5955
Merged
mark-wiemer merged 1 commit intoJun 19, 2026
Merged
Conversation
JoshuaKGoldberg
previously requested changes
May 16, 2026
A “Blocked PR Check” workflow that runs on pull request events (including label changes) and fail whenever a PR has the `status: blocked` label. blocked pull requests can not accidentally pass required checks and get manually merged in anyway.
mostafaNazari702
force-pushed
the
fix/5924-blocked-pr-check
branch
from
May 16, 2026 15:27
053f650 to
3b80cb6
Compare
mark-wiemer
approved these changes
Jun 19, 2026
3 tasks
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.
PR Checklist
status: accepting prsOverview
A small "Blocked PR Check" workflow that just fails when a PR has the
status: blockedlabel. It runs on normal PR events and when labels get added or removed, so it re-checks whenever someone toggles that state. to actually stop the kind of accidental merges that came up in #5409/#5881, it also needs to be set as a required status check in branch protection i think, that part ain’t handled in the repo itself it has to be configured at the admin level