chore: remove the report web UI from this repo - #209
Open
montycheese wants to merge 1 commit into
Open
Conversation
Collaborator
🟡 Heimdall Review Status
|
The benchmark report UI now lives in base/ui under app/benchmark/. Keeping a second copy here meant two divergent frontends over the same data, and the GitHub Pages build was the only reason this Go repo carried a Node/Vite toolchain. - delete report/ - drop the nodejs workflow (it only linted and tested report/**) - drop the GitHub Pages deploy job from public-benchmarks; the run output is uploaded as a workflow artifact instead - drop the report build/upload steps from examples - drop the build-frontend / run-frontend make targets - repoint README, configs/README, the cursor rule, and the data contract doc at docs/report-data-contract.md and the UI's new home The data contract is unchanged: this repo remains a producer, and docs/report-data-contract.md is the interface consumers code against.
montycheese
force-pushed
the
chore/remove-report-ui
branch
from
August 14, 2026 14:42
dda5234 to
d9b331d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Deletes
report/(the Vite/React dashboard) from this repo. The benchmarkreport UI now lives in
base/uiunderapp/benchmark/. Keeping a second copy here meant two divergent frontends overthe same data, and the GitHub Pages build was the only reason this Go repo
carried a Node/Vite toolchain at all.
report/(96 files).github/workflows/nodejs.yaml— it only linted and testedreport/**public-benchmarks.yaml: drop the report build and the whole GitHub Pagesdeployjob; upload the run output as a workflow artifact insteadexamples.yaml: drop the "Build Report" and "Upload Report" stepsMakefile: drop thebuild-frontendandrun-frontendtargetsREADME.md,configs/README.md,.cursor/rules/project-structure.mdc,and
docs/report-data-contract.mdat the data contract and the UI's new homeThe data contract is unchanged. This repo stays a producer, and
docs/report-data-contract.mdremains the interface consumers code against.Follow-up (not in this PR)
Deleting the source does not take the existing https://base.github.io/benchmark/
deployment offline. The last published build stays live until Pages is disabled
in the repo settings, and the repo's homepage URL still points there. Both need
a manual change.
Testing
go build ./...andgo test ./...unaffected — no Go files touched.js-yaml).report/, the Pages URL, andthe dashboard; none left outside the intentional "this repo no longer ships a
dashboard" note in the README.