{"owner":"prometheus-community","repo":"helm-charts","hasSkills":true,"hasMcp":false,"mcpConfig":null,"found":["AGENTS.md",".github/copilot-instructions.md"],"skills":{"AGENTS.md":"# Instructions for AI Agents\n\nThe following guidelines apply to all files in this repository.\n\n## Repository Overview\n\nThis is the **Grafana Community Helm Charts** repository — a collection of Helm charts for Grafana ecosystem components. Charts are published to both a Helm repository (`prometheus-community`) and as OCI artifacts on `ghcr.io`.\n\n## Charts\n\nAll charts live under `charts/` with a subfolder for each chart.  The subfolder names must match the chart name as described in the Chart.yaml file `.name`.\n\nEach chart follows standard Helm structure (`Chart.yaml`, `values.yaml`, `templates/`). Some charts will organize components into subdirectories (e.g., `templates/compactor/`, `templates/ingester/`).\n\n## Feature Implementation Workflow\n\nMost agent tasks in this repository are chart feature changes. For these tasks:\n\n1. Identify the affected chart under `charts/<chart>/` and keep changes scoped to that chart.\n2. Read the relevant `Chart.yaml`, `values.yaml`, templates, helpers, and existing tests before editing.\n3. Implement the feature using the chart's existing template style and values structure.\n4. If `values.yaml` changes in a schema-enabled chart, update schema annotations and regenerate `values.schema.json`.\n5. Add or update focused helm-unittest coverage for the rendered behavior controlled by the feature.\n6. Bump the chart version in `Chart.yaml` according to SemVer.\n7. Run the relevant validation commands, normally `make helm-unittest HELM_CHART=<chart-name>` and any required schema generation command.\n\nAsk the user for clarification only when the intended chart, feature behavior, or compatibility impact cannot be inferred from the request and local context.\n\n## Values Schema\n\nSome charts generate `values.schema.json` from `values.yaml` using `helm-values-schema-json`. A chart uses this flow if `values.yaml` contains `# @schema` comments or a top-level `# $schema: ./values.schema.json` comment. Upstream documentation lives at https://github.com/losisin/helm-values-schema-json/blob/main/docs/README.md; use Context7 for current docs when available.\n\nHelm validates chart values with JSON Schema draft-07. Keep generated schemas compatible with draft-07 even if external schema tooling supports newer drafts.\n\nWhen changing `values.yaml` in a schema-enabled chart:\n\n- Use the `helm-values-schema` skill for detailed schema annotation and regeneration rules.\n- Preserve and update nearby `# @schema` annotations.\n- Add `# @schema` annotations when inferred schema types would be wrong or too loose.\n- Keep `# @schema` comments before helm-docs comments (`# -- ...`) when both are present.\n- Regenerate `values.schema.json` and include it in the change.\n- For Loki, run `make helm-schema HELM_CHART=loki`.\n- Add or update helm-unittest coverage for rendered behavior controlled by the changed values.\n\n## pre-commit testing\n\n### helm-unittests\n\nPull Requests against this repository require that all charts which implement helm-unittests(https://github.com/helm-unittest/helm-unittest) must pass all of their unittests.  This can be done via a single command run from the repository root:\n\n```bash\nmake helm-unittest HELM_CHART=<chart-name>\n```\n\n## Contributing Conventions\n\n- **One chart per PR**: CI enforces that PRs only change a single chart.\n- **PR title format**: Must start with `[chart-name] ` (e.g., `[grafana] Add new feature`).\n- **Version bumps**: Every chart change (excluding files listed in `.helmignore`) requires a SemVer version bump in `Chart.yaml`. Major bumps for breaking changes.\n- **DCO sign-off**: Commits must include `Signed-off-by` line (`git commit -s`).\n- **Squash merge only**: The repository only allows squash merges.\n- **CODEOWNERS/MAINTAINERS**: Auto-generated from `Chart.yaml` maintainer entries by `scripts/generate-codeowners.sh` and `scripts/generate-maintainers.sh`. Do not edit `.github/CODEOWNERS` or `MAINTAINERS.md` directly.\n- **Minimum Kubernetes version**: Charts target `^1.25.0-0` (`kubeVersion` in `Chart.yaml`).\n\n## Dependency Management\n\nRenovate manages all dependency updates.\n",".github/copilot-instructions.md":"# GitHub Copilot Instructions\n\nFollow the repository-wide agent guidance in `AGENTS.md`. This repository contains Helm charts for Prometheus ecosystem components.\n\nMost tasks are Helm chart feature changes. When changing a chart:\n\n- Work within a single chart under `charts/<chart>/`.\n- Read `Chart.yaml`, `values.yaml`, relevant templates, helpers, and existing tests before editing.\n- Follow existing chart patterns before adding new structure.\n- Update `values.yaml`, templates, tests, and generated schema artifacts together when a new value changes rendered behavior.\n- If `values.yaml` contains `# @schema` comments or `# $schema: ./values.schema.json`, follow the `helm-values-schema` skill guidance and regenerate `values.schema.json`.\n- Add or update helm-unittest coverage for rendered behavior changed by templates or values.\n- Run `make helm-unittest HELM_CHART=<chart-name>` for charts with helm-unittest coverage.\n- Bump the chart version in `Chart.yaml` for chart changes not ignored by `.helmignore`.\n- Do not edit generated ownership files such as `.github/CODEOWNERS` or `MAINTAINERS.md` directly.\n"},"files":{"AGENTS.md":"# Instructions for AI Agents\n\nThe following guidelines apply to all files in this repository.\n\n## Repository Overview\n\nThis is the **Grafana Community Helm Charts** repository — a collection of Helm charts for Grafana ecosystem components. Charts are published to both a Helm repository (`prometheus-community`) and as OCI artifacts on `ghcr.io`.\n\n## Charts\n\nAll charts live under `charts/` with a subfolder for each chart.  The subfolder names must match the chart name as described in the Chart.yaml file `.name`.\n\nEach chart follows standard Helm structure (`Chart.yaml`, `values.yaml`, `templates/`). Some charts will organize components into subdirectories (e.g., `templates/compactor/`, `templates/ingester/`).\n\n## Feature Implementation Workflow\n\nMost agent tasks in this repository are chart feature changes. For these tasks:\n\n1. Identify the affected chart under `charts/<chart>/` and keep changes scoped to that chart.\n2. Read the relevant `Chart.yaml`, `values.yaml`, templates, helpers, and existing tests before editing.\n3. Implement the feature using the chart's existing template style and values structure.\n4. If `values.yaml` changes in a schema-enabled chart, update schema annotations and regenerate `values.schema.json`.\n5. Add or update focused helm-unittest coverage for the rendered behavior controlled by the feature.\n6. Bump the chart version in `Chart.yaml` according to SemVer.\n7. Run the relevant validation commands, normally `make helm-unittest HELM_CHART=<chart-name>` and any required schema generation command.\n\nAsk the user for clarification only when the intended chart, feature behavior, or compatibility impact cannot be inferred from the request and local context.\n\n## Values Schema\n\nSome charts generate `values.schema.json` from `values.yaml` using `helm-values-schema-json`. A chart uses this flow if `values.yaml` contains `# @schema` comments or a top-level `# $schema: ./values.schema.json` comment. Upstream documentation lives at https://github.com/losisin/helm-values-schema-json/blob/main/docs/README.md; use Context7 for current docs when available.\n\nHelm validates chart values with JSON Schema draft-07. Keep generated schemas compatible with draft-07 even if external schema tooling supports newer drafts.\n\nWhen changing `values.yaml` in a schema-enabled chart:\n\n- Use the `helm-values-schema` skill for detailed schema annotation and regeneration rules.\n- Preserve and update nearby `# @schema` annotations.\n- Add `# @schema` annotations when inferred schema types would be wrong or too loose.\n- Keep `# @schema` comments before helm-docs comments (`# -- ...`) when both are present.\n- Regenerate `values.schema.json` and include it in the change.\n- For Loki, run `make helm-schema HELM_CHART=loki`.\n- Add or update helm-unittest coverage for rendered behavior controlled by the changed values.\n\n## pre-commit testing\n\n### helm-unittests\n\nPull Requests against this repository require that all charts which implement helm-unittests(https://github.com/helm-unittest/helm-unittest) must pass all of their unittests.  This can be done via a single command run from the repository root:\n\n```bash\nmake helm-unittest HELM_CHART=<chart-name>\n```\n\n## Contributing Conventions\n\n- **One chart per PR**: CI enforces that PRs only change a single chart.\n- **PR title format**: Must start with `[chart-name] ` (e.g., `[grafana] Add new feature`).\n- **Version bumps**: Every chart change (excluding files listed in `.helmignore`) requires a SemVer version bump in `Chart.yaml`. Major bumps for breaking changes.\n- **DCO sign-off**: Commits must include `Signed-off-by` line (`git commit -s`).\n- **Squash merge only**: The repository only allows squash merges.\n- **CODEOWNERS/MAINTAINERS**: Auto-generated from `Chart.yaml` maintainer entries by `scripts/generate-codeowners.sh` and `scripts/generate-maintainers.sh`. Do not edit `.github/CODEOWNERS` or `MAINTAINERS.md` directly.\n- **Minimum Kubernetes version**: Charts target `^1.25.0-0` (`kubeVersion` in `Chart.yaml`).\n\n## Dependency Management\n\nRenovate manages all dependency updates.\n",".github/copilot-instructions.md":"# GitHub Copilot Instructions\n\nFollow the repository-wide agent guidance in `AGENTS.md`. This repository contains Helm charts for Prometheus ecosystem components.\n\nMost tasks are Helm chart feature changes. When changing a chart:\n\n- Work within a single chart under `charts/<chart>/`.\n- Read `Chart.yaml`, `values.yaml`, relevant templates, helpers, and existing tests before editing.\n- Follow existing chart patterns before adding new structure.\n- Update `values.yaml`, templates, tests, and generated schema artifacts together when a new value changes rendered behavior.\n- If `values.yaml` contains `# @schema` comments or `# $schema: ./values.schema.json`, follow the `helm-values-schema` skill guidance and regenerate `values.schema.json`.\n- Add or update helm-unittest coverage for rendered behavior changed by templates or values.\n- Run `make helm-unittest HELM_CHART=<chart-name>` for charts with helm-unittest coverage.\n- Bump the chart version in `Chart.yaml` for chart changes not ignored by `.helmignore`.\n- Do not edit generated ownership files such as `.github/CODEOWNERS` or `MAINTAINERS.md` directly.\n"},"items":[{"name":"AGENTS.md","path":"AGENTS.md","title":"AGENTS.md","content":"# Instructions for AI Agents\n\nThe following guidelines apply to all files in this repository.\n\n## Repository Overview\n\nThis is the **Grafana Community Helm Charts** repository — a collection of Helm charts for Grafana ecosystem components. Charts are published to both a Helm repository (`prometheus-community`) and as OCI artifacts on `ghcr.io`.\n\n## Charts\n\nAll charts live under `charts/` with a subfolder for each chart.  The subfolder names must match the chart name as described in the Chart.yaml file `.name`.\n\nEach chart follows standard Helm structure (`Chart.yaml`, `values.yaml`, `templates/`). Some charts will organize components into subdirectories (e.g., `templates/compactor/`, `templates/ingester/`).\n\n## Feature Implementation Workflow\n\nMost agent tasks in this repository are chart feature changes. For these tasks:\n\n1. Identify the affected chart under `charts/<chart>/` and keep changes scoped to that chart.\n2. Read the relevant `Chart.yaml`, `values.yaml`, templates, helpers, and existing tests before editing.\n3. Implement the feature using the chart's existing template style and values structure.\n4. If `values.yaml` changes in a schema-enabled chart, update schema annotations and regenerate `values.schema.json`.\n5. Add or update focused helm-unittest coverage for the rendered behavior controlled by the feature.\n6. Bump the chart version in `Chart.yaml` according to SemVer.\n7. Run the relevant validation commands, normally `make helm-unittest HELM_CHART=<chart-name>` and any required schema generation command.\n\nAsk the user for clarification only when the intended chart, feature behavior, or compatibility impact cannot be inferred from the request and local context.\n\n## Values Schema\n\nSome charts generate `values.schema.json` from `values.yaml` using `helm-values-schema-json`. A chart uses this flow if `values.yaml` contains `# @schema` comments or a top-level `# $schema: ./values.schema.json` comment. Upstream documentation lives at https://github.com/losisin/helm-values-schema-json/blob/main/docs/README.md; use Context7 for current docs when available.\n\nHelm validates chart values with JSON Schema draft-07. Keep generated schemas compatible with draft-07 even if external schema tooling supports newer drafts.\n\nWhen changing `values.yaml` in a schema-enabled chart:\n\n- Use the `helm-values-schema` skill for detailed schema annotation and regeneration rules.\n- Preserve and update nearby `# @schema` annotations.\n- Add `# @schema` annotations when inferred schema types would be wrong or too loose.\n- Keep `# @schema` comments before helm-docs comments (`# -- ...`) when both are present.\n- Regenerate `values.schema.json` and include it in the change.\n- For Loki, run `make helm-schema HELM_CHART=loki`.\n- Add or update helm-unittest coverage for rendered behavior controlled by the changed values.\n\n## pre-commit testing\n\n### helm-unittests\n\nPull Requests against this repository require that all charts which implement helm-unittests(https://github.com/helm-unittest/helm-unittest) must pass all of their unittests.  This can be done via a single command run from the repository root:\n\n```bash\nmake helm-unittest HELM_CHART=<chart-name>\n```\n\n## Contributing Conventions\n\n- **One chart per PR**: CI enforces that PRs only change a single chart.\n- **PR title format**: Must start with `[chart-name] ` (e.g., `[grafana] Add new feature`).\n- **Version bumps**: Every chart change (excluding files listed in `.helmignore`) requires a SemVer version bump in `Chart.yaml`. Major bumps for breaking changes.\n- **DCO sign-off**: Commits must include `Signed-off-by` line (`git commit -s`).\n- **Squash merge only**: The repository only allows squash merges.\n- **CODEOWNERS/MAINTAINERS**: Auto-generated from `Chart.yaml` maintainer entries by `scripts/generate-codeowners.sh` and `scripts/generate-maintainers.sh`. Do not edit `.github/CODEOWNERS` or `MAINTAINERS.md` directly.\n- **Minimum Kubernetes version**: Charts target `^1.25.0-0` (`kubeVersion` in `Chart.yaml`).\n\n## Dependency Management\n\nRenovate manages all dependency updates.\n","category":"root","tokens":1020},{"name":"copilot-instructions.md","path":".github/copilot-instructions.md","title":"copilot-instructions.md","content":"# GitHub Copilot Instructions\n\nFollow the repository-wide agent guidance in `AGENTS.md`. This repository contains Helm charts for Prometheus ecosystem components.\n\nMost tasks are Helm chart feature changes. When changing a chart:\n\n- Work within a single chart under `charts/<chart>/`.\n- Read `Chart.yaml`, `values.yaml`, relevant templates, helpers, and existing tests before editing.\n- Follow existing chart patterns before adding new structure.\n- Update `values.yaml`, templates, tests, and generated schema artifacts together when a new value changes rendered behavior.\n- If `values.yaml` contains `# @schema` comments or `# $schema: ./values.schema.json`, follow the `helm-values-schema` skill guidance and regenerate `values.schema.json`.\n- Add or update helm-unittest coverage for rendered behavior changed by templates or values.\n- Run `make helm-unittest HELM_CHART=<chart-name>` for charts with helm-unittest coverage.\n- Bump the chart version in `Chart.yaml` for chart changes not ignored by `.helmignore`.\n- Do not edit generated ownership files such as `.github/CODEOWNERS` or `MAINTAINERS.md` directly.\n","category":".github","tokens":279}]}