kodor/* labels are defined at both repo and org scope #22

New Issue

2026-08-23T23:38:45-04:00

jared commented

2026-08-23 23:38:45 -04:00

Five kodor/* label names exist at both repo and org scope with
different IDs:

name	repo id	org id
`kodor`	223	300
`kodor/fix`	224	301
`kodor/feature-proposal`	225	302
`kodor/triaged`	226	303
`kodor/needs-review`	227	304

Two consequences:

Filtering by name is ambiguous. An issue can carry both copies, and a query
for kodor/triaged may match one, the other, or both depending on which ID was
applied.
They are not exclusive. Scoped labels that are not exclusive render flat and
enforce nothing, so an issue can hold kodor/fix and kodor/feature-proposal
at once.

Compass reports this but will never change it — making an org-level label exclusive
would alter rendering across every repository in the organisation.

Decide: which scope wins. Delete the losing copies, make the survivors exclusive,
and re-apply to any issue that carried the deleted ID.

Five `kodor/*` label names exist at **both** repo and org scope with different IDs: | name | repo id | org id | |---|---|---| | `kodor` | 223 | 300 | | `kodor/fix` | 224 | 301 | | `kodor/feature-proposal` | 225 | 302 | | `kodor/triaged` | 226 | 303 | | `kodor/needs-review` | 227 | 304 | Two consequences: 1. **Filtering by name is ambiguous.** An issue can carry both copies, and a query for `kodor/triaged` may match one, the other, or both depending on which ID was applied. 2. **They are not exclusive.** Scoped labels that are not exclusive render flat and enforce nothing, so an issue can hold `kodor/fix` and `kodor/feature-proposal` at once. Compass reports this but will never change it — making an org-level label exclusive would alter rendering across every repository in the organisation. **Decide:** which scope wins. Delete the losing copies, make the survivors exclusive, and re-apply to any issue that carried the deleted ID.

jared added the

labels 2026-08-23 23:38:46 -04:00

jared referenced this issue

2026-08-23 23:39:11 -04:00

Project status #23

jared referenced this issue from a commit

2026-08-24 00:15:19 -04:00

docs: record session (#21, #22)