Skip to content

docs: point the 4 rich benchmark READMEs at their relocated chart preset#27

Merged
elronbandel merged 1 commit into
mainfrom
elron/rich-readme-presets-v2
Jun 3, 2026
Merged

docs: point the 4 rich benchmark READMEs at their relocated chart preset#27
elronbandel merged 1 commit into
mainfrom
elron/rich-readme-presets-v2

Conversation

@elronbandel

Copy link
Copy Markdown
Contributor

Why

Follow-up to the self-contained-chart migration (#26). That PR moved the bespoke k8s topology for the 4 rich benchmarks from benchmarks/<x>/values.yaml into benchmarks/_chart/presets/<x>.yaml — but their per-benchmark README.md "Files" sections still listed only Dockerfile / compose.yaml / README.md. A reader of, say, osworld's README (described as needing a desktop sidecar) had no pointer to where that k8s config now lives.

What

Add one "Files" entry to each of osworld, tau-bench, visualwebarena, webarena pointing at its benchmarks/_chart/presets/<x>.yaml, noting it's the benchmark's bespoke k8s topology overlaid on the shared chart when rendered with --set benchmark=<x>.

4 files, +4 lines. No code, no behavior change.

The bespoke k8s topology for osworld/tau-bench/visualwebarena/webarena moved
from benchmarks/<x>/values.yaml into benchmarks/_chart/presets/<x>.yaml, but
their README 'Files' sections still only listed Dockerfile/compose.yaml — a
reader had no pointer to where the sidecar/Deployment config now lives. Add a
Files entry for each pointing at its preset.
@elronbandel elronbandel merged commit e4692bb into main Jun 3, 2026
1 check failed
elronbandel added a commit that referenced this pull request Jun 15, 2026
docs: point the 4 rich benchmark READMEs at their relocated chart preset
elronbandel added a commit that referenced this pull request Jun 15, 2026
docs: point the 4 rich benchmark READMEs at their relocated chart preset
elronbandel added a commit that referenced this pull request Jun 15, 2026
docs: point the 4 rich benchmark READMEs at their relocated chart preset
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant