Re-enable cosmetic yamllint rules after normalizing vendored manifests
- Lenguaje dominante
- Python
- Estrellas
- 1
- Forks
- 0
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
To get CI green on the initial publish, `.yamllint` disables several cosmetic rules (`indentation`, `colons`, `braces`, `document-start`, `line-length`) that the vendored upstream manifests do not follow. Structural checks (syntax, duplicate keys, empty values, trailing whitespace) remain enabled.
**Action (optional, quality)**: progressively normalize the vendored YAML (consistent indentation, `---` document starts, brace/colon spacing) and re-enable the corresponding rules. `line-length` should stay disabled because some manifests embed machine-generated Grafana dashboard JSON on single long lines.
Context: see the CI setup in `.github/workflows/ci.yml` and `.yamllint`.
---
Generated by Coder Agents, on behalf of @ausbru87.
Guía de contribución
Línea de trabajo
Start with .yamllint and .github/workflows/ci.yml, then inspect the vendored YAML manifests that currently violate the cosmetic rules. Normalize indentation, document starts, and brace/colon spacing where practical, re-enable those rules, keep line-length disabled for generated dashboard JSON, and verify CI remains green.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- github-actions, yaml
- Área
- ci-cd, devops
- Tipo de issue
- Refactorización
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Tranquilo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 48/100