Org labels S4: priority moves from labels to an org Priority issue field

Abierto
#14,074 8 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github, shell
Área
tooling

Línea de trabajo

Start with parent issue #14068 for the change table and reader inventory, then inspect ci-workflows intake triage and work-items for uses of priority: labels. Check the github-iac ADR 0016 pattern and the expected-org-security record once the owner creates the Priority field and provides its ids. Done means triage and work-items read and set the field, open issues receive its value, and the saved label item lists are followed by deleting the priority: labels.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

priority: medium

Outcome

Problem: priority is a single-value fact kept as four labels, which nothing native keeps to one value; GitHub's issue fields provide a single-select field for it.

  • Intent (why, in the user's words): "Now's our chance to get the labels correct."

Parent: #14068 (the change table and the reader inventory are there).

Waits on the owner creating the Priority issue field in org settings (the pattern github-iac ADR 0016 records for Size, Complexity and Uncertainty), and on its ids being added to github-iac's expected-org-security record.

Done when

  • ci-workflows intake triage sets and reads the Priority field instead of priority: labels.
  • work-items reads priority from the field (work_priority_order no longer requires the priority: pattern).
  • Open issues carry the field value; the priority: labels are deleted after their item lists are saved.
Lenguaje dominante
Shell
Estrellas
22
Forks
2
Merge medio
56 min
PR fusionados (30 d)
959

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de melodic-software/claude-code-plugins

Todos los issues de melodic-software/claude-code-plugins

Issues similares

Más issues de Shell/Bash

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.