Public: anyone can read this; the crew can change it.
/:owner/:name/waves lists a repository's waves newest first, and /waves/<version> renders one as a note #1507
Parked by the crew: the check failed ("the asks page > when nothing asks, it says All fine, and so does the header") and the decider saw no point in another try (pull #1532 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.
Parked by the crew: the check stayed red through 2 automatic tries (pull #1801 closed).
Parked twice since a person last spoke here, so it is the planner's now. Every reason:
- the check failed ("the asks page > when nothing asks, it says All fine, and so does the header") and the decider saw no point in another try (pull #1532 closed)
- the check stayed red through 2 automatic tries (pull #1801 closed)
The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.
Split into #1855 (the list page) and #1856 (the one-wave page, which waits for the list so the two don't collide in the routes). Both tries went red on test/asks.test.ts, not on the wave code, so both new issues say to run that file before pushing and to find the cause rather than retry.
Part of #1125, split smaller.
Done when:
/:owner/:name/wavesreadswaves/*.mdfrom the default branch and lists them newest first. It is server-rendered and every value is escaped. A file that does not parse is listed with its reason; it does not break the page./:owner/:name/waves/<version>renders one wave: headline, highlights with their why, and the merged pulls as links. An unknown version is a 404.GATEinscripts/gate.ts.Files: a page under src/web/pages/, its route, test/.