Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Feedback request: ran a config-diff tool against PR #1663 — is this useful on chart values?

Abierto
  • ¿Algo no está bien?
#1,671 0 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
yaml
Área
devops

Línea de trabajo

Start by reviewing PR #1663 and the cited charts/*/values.yaml changes, then compare the Flecto output with the raw diff and the repository's current review or CI workflow. This issue is done when maintainers decide whether changed-path comments provide useful signal at this repository's volume; no implementation scope is specified.

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

Descripción

Hi — apologies for arriving via the issue tracker. This is a feedback request rather than a bug report, and "not interested" is a completely fine answer; I'll close it myself if so.

I maintain Flecto, a small open-source tool that reports what a config change actually did, in plain English, as a pull request comment. I've been running it against real repositories rather than my own fixtures, because fixtures tell you nothing about whether the output is useful.

I ran it read-only against your PR #1663 ("remove placeholder values from monitoring chart"):

✅ Check passing — 2 changes in 1 file — 2 changed, 0 added, 0 removed.
Policy: no findings.

| changed | prometheus.server.alertmanagers[0].relabel_configs[0].regex | "<namespace>"    | "monitoring" |
| changed | prometheus.server.alertmanagers[0].relabel_configs[1].regex | "<release-name>" | "monitoring" |

The reason I picked this PR: those two values sit five levels down inside
relabel_configs, and in a raw YAML diff they are two lines that look like every other two lines. Naming the full path and the before/after is most of what I am trying to test — whether that framing actually helps a reviewer, or whether it is just the same information rearranged.

Two questions, neither of which needs you to install anything:

  1. When a PR touches charts/*/values.yaml in this repo, what do you look at today? Rendered output, the raw diff, or mostly trust plus CI?
  2. With 1600+ PRs, would a comment naming changed paths be signal or noise here?

If the honest answer to 2 is "noise at our volume", that is genuinely the more useful answer for me, and I would rather hear it.

Happy to close this right away if issue-tracker outreach isn't welcome — just say so.

Lenguaje dominante
Rust
Estrellas
7
Forks
6
Merge medio
1 d 31 min
PR fusionados (30 d)
83

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 DiamondLightSource/workflows

Todos los issues de DiamondLightSource/workflows

Issues similares

Más issues de Rust

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.