docs(runbooks): record priority band definitions in triage - #545
Merged
Conversation
The public wiki carried a priority definition table that no runbook duplicated, so removing maintainer content from the wiki per ADR 0006 would have dropped it. Record the bands here, where triage classification already lives, and note that `priority:high` covers only the top two.
ss-o
force-pushed
the
docs/triage-priority-bands
branch
from
August 27, 2026 21:47
d676af5 to
0c373c1
Compare
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
1 participant
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
Records the priority band definitions in the triage runbook.
The public wiki carried a priority definition table that no runbook duplicated. Removing maintainer content from the wiki per ADR 0006 would have dropped it, so it lands here, next to the triage classification tables that already exist.
Why here
runbooks/triage.mdalready owns the label classification tables and the Project 28 field-setting procedure. Priority semantics belong with them rather than on a public contributor-facing page.Also notes that
priority:highcovers only the top two bands, since the label set has nopriority:criticaland the distinction was previously implicit.Related
Paired with z-shell/wiki#871 which removes the maintainer-only surface from the public wiki. That PR links back to this runbook, so merging this one first avoids a dangling reference.
Verification
lib/labels.ymlstill parses