You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Monolithic index.html and api-reference.md make every v5 PR conflict with every other #15299
Nearly every PR to v5 conflicts with every other PR to v5, because two monolithic files are touched by almost all of them:
src/pkg/dashboard/static/index.html — ~60 400 lines: the whole inline style sheet, several hundred JS function groups and every body template in one file. Embedded via //go:embed static, gzipped once at startup, CSP-hashed; many tests assert on its literal HTML/ids/classes and a node harness loads functions from it.
src/docs/api-reference.md — one large route table regenerated by src/scripts/check-api-reference-citations.sh --fix whenever server.go / api.go routes change.
Any two PRs that touch the dashboard (or any route) collide in these files even when their changes are unrelated. After each merge, every open PR has to be rebased, regenerated and re-pushed before Tide will look at it again, and the rebase itself is error-prone (hand-merging unrelated hunks in a 60k-line file).
Evidence (today)
Each of these merges re-conflicted the open dashboard PRs, forcing a rebase round across the queue:
Decompose both files so a PR touches only the area it changes, without changing served bytes or breaking CSP/tests:
Part 1 — dashboard: split index.html into per-area sources under src/pkg/dashboard/static-src/ (head.html, css/<area>.css, js/<area>.js, html/<area>.html, glue files, manifest.txt) and a go:generate concatenator that writes the committed static/index.html. The artifact stays committed and is byte-identical, so the embed, CSP hashes, node harnesses and all existing tests are unchanged. TestIndexHTMLIsGenerated fails when artifact and sources drift; make dashboard-gen regenerates. Conflicts in index.html are resolved by taking the base's copy and regenerating — never by hand (documented in src/docs/dashboard-source-layout.md).
Part 2 — api-reference: split src/docs/api-reference.md into src/docs/api-reference/<area>.md grouped by route prefix / handler file, with api-reference.md becoming an index that keeps existing anchors; check-api-reference-citations.sh walks the directory and --fix writes only the affected area's file.
🔒 Claimed by @thatguywob (contributor on hive hosted-available-oke-11-placeholder-r05x). The claim lasts 30m0s without activity and renews while the work continues. Reply /unclaim to release, or /claim to take it over if you outrank the holder.
Activity
hivecommons-hive commentedon Oct 29, 2026
🔒 Claimed by @thatguywob (contributor on hive hosted-available-oke-11-placeholder-r05x). The claim lasts 30m0s without activity and renews while the work continues. Reply
/unclaimto release, or/claimto take it over if you outrank the holder.hivecommons-hive commentedon Oct 29, 2026
🔓 Claim by @thatguywob released (lease revoked).
🌱 docs: split api-reference into per-area files
🌱 docs: split api-reference into per-area files
🌱 docs: split api-reference into per-area files
🌱 docs: split api-reference into per-area files
🌱 docs: split api-reference into per-area files
🌱 docs: split api-reference into per-area files
🌱 docs: split api-reference into per-area files (hivecommons#15304)