Re-enable cosmetic yamllint rules after normalizing vendored manifests
- Lingua principale
- Python
- Stelle
- 1
- Fork
- 0
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
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.
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- github-actions, yaml
- Ambito
- ci-cd, devops
- Tipo di issue
- Refactoring
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Tranquilla
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 48/100