Reduce the number of labels

Abierto
  • ¿Algo no está bien?
#4,726 1 comentario 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
5/5
Tiempo estimado
1-2 días
Aptitud para principiantes
15/100
Tipo de issue
Refactorización
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
github
Área
developer-experience

Línea de trabajo

No code or test is named; the change is to the repository's issue and pull request labels. Start by reading the proposed label list in the issue body and the maintainers' comments, then offer a view on which labels to merge or keep. Done means maintainers agree on a consensus list and the labels are updated in the repository settings. Design decisions are still open, so check with the maintainers before editing anything.

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

Descripción

It would be nice to reduce the number of labels for issues and pull requests. The more labels there are, the less likely that people will use them effectively or at all. Maybe something like this:

  • Refactor: issues and PRs that are not intended to change the output (or input) at all.
  • Bug: an error in coding, or an error in a model that we know how to fix (as opposed to bigger discussions)
  • Models (excluding cost)
  • Cost models
  • Stellarator
  • Interface: changes in the formatting of the input and output or how the code is used but not the actual equations.
  • Blocked: issues or PRs that can't be worked on until another issue or PR has been resolved.

It turns out that I can actually edit the labels - so if everyone would like to comment on this issue I can propose a consensus list and implement it.

@je-cook @clmould @jmorris-uk @timothy-nunn @chris-ashe @j-a-foster @kj5248 @ajpearcey @OceanNuclear

Lenguaje dominante
Python
Estrellas
75
Forks
29
Merge medio
2 d 13 h
PR fusionados (30 d)
27

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 ukaea/PROCESS

Todos los issues de ukaea/PROCESS

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.