fix(labels): adopt world-at-ruin labels with the full policy set#117
Conversation
world-at-ruin was the only repo of 21 whose IssueLabels CR was still Observe-only, so the canonical 22-label taxonomy was declared but never applied: the repo has 5 live labels and no bug/documentation/refactor, leaving issues like #124 with no honest label. The CR reports Synced/Ready on the live cluster, which is the promotion condition the Observe-only bootstrap named. Additive only: no Delete policy, and all five existing labels are members of the canonical set. Fixes #116 Part of #56
Readiness record — head
|
@codex review |
|
Codex Review: Didn't find any major issues. Delightful! Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
Why
World at Ruin's issues can't be triaged. The repo has only 5 labels — no
bug,documentation,refactor,securityorneeds triage— because its label resource was left in observe-only modewhen the repo was bootstrapped, and the follow-up step to actually start applying labels was never
taken. It is the only one of 21 repositories still in that state. Issue #124 is sitting untriaged
right now for exactly this reason: no label fits it.
What
Switches world-at-ruin's labels to the same managed mode every other repo already uses, so the
standard 22-label set gets applied.
Additive only — the five labels it already has are all part of the standard set, and nothing grants
permission to delete labels, so no existing label is removed or recoloured. The rendered output
changes by exactly three lines, all of them the mode itself.
The condition the bootstrap set for making this switch — the resource reporting healthy against
the live org — is met.
Fixes #116
Part of #56