Add labels for Jenkins/GlitchTip/observability workflow #80

New Issue

2026-07-02T05:46:41-05:00

jcwalker3 commented

2026-07-02 05:46:41 -05:00

Curated 2026-07-02 to reflect review consensus (issue text only; not started).

Approval-gated label proposal. Document the labels first; do not create
or bulk-apply anything without explicit approval.

Proposed labels (with color/description to be filled in the proposal)

jenkins — already exists
glitchtip — already exists
observability — missing
source:glitchtip — missing
status:triage — missing

Acceptance criteria

Documents each label's intended use, plus proposed color + description.
Lists which labels already exist vs missing (see above).
Do not create labels unless explicitly approved.
Do not bulk-apply labels to existing issues.
Do not disturb existing labels.

Note: final label names for observability depend on the #71 namespace decision.

_Curated 2026-07-02 to reflect review consensus (issue text only; not started)._ **Approval-gated label proposal.** Document the labels first; do **not** create or bulk-apply anything without explicit approval. ## Proposed labels (with color/description to be filled in the proposal) * `jenkins` — **already exists** * `glitchtip` — **already exists** * `observability` — **missing** * `source:glitchtip` — **missing** * `status:triage` — **missing** ## Acceptance criteria * Documents each label's intended use, plus proposed color + description. * Lists which labels already exist vs missing (see above). * **Do not create labels unless explicitly approved.** * **Do not bulk-apply labels** to existing issues. * Do not disturb existing labels. Note: final label names for observability depend on the #71 namespace decision.