Re-enable cosmetic yamllint rules after normalizing vendored manifests
- 主要言語
- Python
- スター
- 1
- フォーク
- 0
- PR マージ指標
- 30日以内にマージされた PR はありません
説明
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.
コントリビューションガイド
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
評価
- 技術スタック
- github-actions, yaml
- 領域
- ci-cd, devops
- issue の種類
- リファクタリング
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 活発さ
- 静か
- 明瞭さ
- おおむね明確
- 初心者へのやさしさ
- 48/100